Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Recent update causes docker containers to stop functionning? #1832

Closed
littleblack111 opened this issue May 18, 2024 · 2 comments
Closed
Labels
bug Something isn't working

Comments

@littleblack111
Copy link

littleblack111 commented May 18, 2024

Describe the bug

A clear and concise description of what the bug is.

80% of the docker containers stopped working

To Reproduce
Update to newest update

Steps to reproduce the behavior:

If you try to start then you will see error like:
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: failed to write "536870912": write /sys/fs/cgroup/memory/docker/7d97ad9c62d75eefa49030b582768513f41c444305eeffb27419b150e6b72f1f/memory.soft_limit_in_bytes: operation not supported: unknown

Expected behavior

docker containers to be working

A clear and concise description of what you expected to happen.

https://www.reddit.com/r/CasaOS/comments/1cu6t9f/80_docker_containers_suddently_stopped_working/

Screenshots

https://preview.redd.it/80-docker-containers-suddently-stopped-working-v0-4w1an2luzz0d1.png?width=1004&format=png&auto=webp&s=82dac720fc96e29b163f8619c74e8f1fbaa5b833

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

 - OS: Ubuntu
 - Browser chromium based
 - Version v0.4.9

System Time

Run timedatectl and share the output

               Local time: Sat 2024-05-18 16:17:40 HKT
           Universal time: Sat 2024-05-18 08:17:40 UTC
                 RTC time: Sat 2024-05-18 08:17:40
                Time zone: Asia/Hong_Kong (HKT, +0800)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

Logs

Run following command to collect corresponding logs:

sudo journalctl -xef -u casaos-gateway
sudo journalctl -xef -u casaos-user-service
sudo journalctl -xef -u casaos-local-storage
sudo journalctl -xef -u casaos-app-management
sudo journalctl -xef -u casaos.service

casaos-user-service.txt
casaos-local-storage.txt
casaos-gateway.txt
casaos-app-managment.txt
casaos.txt

Additional context

Add any other context about the problem here.
just updated, worked for a few hours then this started happening.
https://www.reddit.com/r/CasaOS/comments/1cu6t9f/80_docker_containers_suddently_stopped_working/
If you are a Zimaboard user, make it explicit with when you got your Zimaboard.

@littleblack111 littleblack111 added the bug Something isn't working label May 18, 2024
@littleblack111
Copy link
Author

it's a week already? Anyone?

@littleblack111
Copy link
Author

[https://www.reddit.com/r/CasaOS/comments/1cu6t9f/80_docker_containers_suddently_stopped_working/](> Solved guys.

Solutions:

To enable cgroups accounting, you must boot Linux with the command line parameters cgroup_enable=memory swapaccount=1.

if that didnt work, and you're using a real time kernel, then try a normal/generic kernel

If that still didn't work, then downgrade the kernel)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant