Stefan_H

Members
  • Posts

    3
  • Joined

  • Last visited

Stefan_H's Achievements

Noob

Noob (1/14)

4

Reputation

  1. I have the same issue, very high cpu (up to 300%) and ram utilization by the dockerd service even with 0 docker containers running. If i stop the dockerd service the cpu utilization drops to below 5% overall. If i start a container I can't even use / access the GUI (because of the system load i guess). Also can't easily downgrade to unraid version 6.11.5 because i downloaded 6.12.1 and only 6.12 is being shown as a downgrade option in the update os panel so I did not try if that fixes the issue. Update: Waited one day with the server running but dockerd stopped. Then started it up again with /etc/rc.d/rc.docker start and now dockers work normally again.
  2. I also just got this Error because my System ran out of memory and from the logs i could tell that it killed the process with the highest memory consumption (dockerd). What worked for me was just running /etc/rc.d/rc.docker start in the Terminal to start it up again. Will of course not work if the docker image is really corrupt, but might be worth a try in cases similar to mine.
  3. What worked for me was editing the '/boot/config/docker.cfg' file with $ nano /boot/config/docker.cfg and appending: DOCKER_OPTS="--insecure-registry YOUR_REGISTRY_IP:YOUR_REGISTRY_PORT" Then you need to restart the docker service to apply the changes with: $ /etc/rc.d/rc.docker restart This is also persistent across reboots.