Docker service can't be started

[maddin (M. Dro_ste)]

Hi everybody,

all went really good - until I tried to change the running system…needed greater storage…

So what happened - I do not know but after cloning the system SD there was no boot possible just blinking cursor…tried to repair but didn’t worked so i decided to reinstall and try the backup.

The Backup? - well I did a lot off anomalous things with my system… so better than nothing but not perfect…

After the backup even the docker an portainer was running without containers an images but well…but when I tried to get an Image there have been no space available.

My recherche(well mine!!!) told me that …docker/overlay2 folder was too big…took 110g from 111G…the hole system stop running…but It had to because of my daughters…long story! So I tried to deinstall docker.

But at least it was the Nextcloudapp backup(prepared to backup in 3 weeks…) which took all the space…grrr.

Ok now I reinstalled in Cockpit - but didn’t started, there has been a second one docker_CE-cli - I removed and tried again…ok Docker had been installed.

But know I can’t start the service - here the command with problems

Fehler

dns.service_action_error

echo ‘{“action”:“start”,“name”:“docker”}’ | /usr/bin/setsid /usr/bin/sudo /usr/libexec/nethserver/api/system-services/update | jq

At this point I have no idea where or what to control!?

THX for all suggestions

maddin

[mrmarkuz (Markus Neuberger)]

Please try to start the service on command line:

systemctl restart docker

Let’s check the docker service status:

systemctl status docker -l

Maybe there’s more information about the error in /var/log/messages logfile?

[maddin (M. Dro_ste)]

@mrmarkuz

systemctl restart docker

Blockquote
[root@central ~]# systemctl restart docker
Job for docker.service failed because the control process exited with error code. See “systemctl status docker.service” and “journalctl -xe” for details.
[root@central ~]# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/docker.service.d
└─nethserver.conf
Active: failed (Result: start-limit) since Wed 2022-09-07 12:24:58 CEST; 28s ago
Docs: https://docs.docker.com
Process: 6509 ExecStartPost=/usr/libexec/dockerRestartPortainer (code=exited, status=1/FAILURE)
Process: 6502 ExecStartPost=/usr/libexec/dockerCreateMacVlan0 (code=exited, status=0/SUCCESS)
Process: 6344 ExecStart=/usr/bin/dockerd --config-file=/etc/docker/docker.conf (code=exited, status=0/SUCCESS)
Main PID: 6344 (code=exited, status=0/SUCCESS)
Sep 07 12:24:56 central.blablabla.lan systemd[1]: Failed to start Docker Application Container Engine.
Sep 07 12:24:56 central.blablabla.lan systemd[1]: Unit docker.service entered failed state.
Sep 07 12:24:56 central.blablabla.lan systemd[1]: docker.service failed.
Sep 07 12:24:58 central.blablabla.lan systemd[1]: docker.service holdoff time over, scheduling restart.
Sep 07 12:24:58 central.blablabla.lan systemd[1]: Stopped Docker Application Container Engine.
Sep 07 12:24:58 central.blablabla.lan systemd[1]: start request repeated too quickly for docker.service
Sep 07 12:24:58 central.blablabla.lan systemd[1]: Failed to start Docker Application Container Engine.
Sep 07 12:24:58 central.blablabla.lan systemd[1]: Unit docker.service entered failed state.
Sep 07 12:24:58 central.blablabla.lan systemd[1]: docker.service failed.
[root@central ~]# journalctl -xe
Sep 07 12:24:58 central.blablabla.lan systemd[1]: Starting Docker Socket for the API.
– Subject: Unit docker.socket has begun start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
–
– Unit docker.socket has begun starting up.
Sep 07 12:24:58 central.blablabla.lan systemd[1]: Listening on Docker Socket for the API.
– Subject: Unit docker.socket has finished start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
–
– Unit docker.socket has finished starting up.
–
– The start-up result is done.
Sep 07 12:24:58 central.blablabla.lan systemd[1]: start request repeated too quickly for docker.service
Sep 07 12:24:58 central.blablabla.lan systemd[1]: Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
–
– Unit docker.service has failed.
–
– The result is failed.
Sep 07 12:24:58 central.blablabla.lan systemd[1]: Unit docker.service entered failed state.
Sep 07 12:24:58 central.blablabla.lan systemd[1]: docker.service failed.
Sep 07 12:25:01 central.blablabla.lan systemd[1]: Created slice User Slice of apache.
– Subject: Unit user-48.slice has finished start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

If I know how to repair portainer…

Thx for your help

Martin

[mrmarkuz (Markus Neuberger)]

Here is a way to reinstall portainer:

Portainer config issues

OK, let’s remove portainer container and recreate it. Be sure to get the right container ID of portainer: docker ps -a Remove it! docker rm -f <container ID> Check if it’s deleted: docker ps -a Just to be sure we delete the image too, get the image ID: docker images -a Remove images: docker rmi -f <image> ID Recreate portainer container (it’s recreated if it doesn’t exist): signal-event nethserver-docker-update Check if portainer is started now: docker ps -a

Maybe you need to completely remove the portainer files too:

Portainer config issues

I think you’re hitting this one: You need to delete the content of the local portainer directory and restart: rm -Rf /var/lib/nethserver/portainer/* signal-event nethserver-docker-update

[maddin (M. Dro_ste)]

@Portainer config issues

rm -Rf /var/lib/nethserver/portainer/* signal-event nethserver-docker-update

hmmm,

I think it was my panic attack but i needed nextcloud to work quick…

Sep 7 13:13:16 central dockerd: time=“2022-09-07T13:13:16.663824845+02:00” level=warning msg=“error locating sandbox id 2069ddba785bc2ca9fb4c2e4251a9f117933fcb2d9c4a063dd20b8df4612ce57: sandbox 2069ddba785bc2ca9fb4c2e4251a9f117933fcb2d9c4a063dd20b8df4612ce57 not found”
Sep 7 13:13:16 central dockerd: time=“2022-09-07T13:13:16.665536525+02:00” level=error msg=“506f41ceaf3b9b9c101407abe752cc1b22751446d58741550e1f963b3ad1a7d7 cleanup: failed to delete container from containerd: no such container”
Sep 7 13:13:16 central dockerd: time=“2022-09-07T13:13:16.665633129+02:00” level=error msg=“Failed to start container 506f41ceaf3b9b9c101407abe752cc1b22751446d58741550e1f963b3ad1a7d7: stat /var/lib/docker/overlay2/3301f9fe53e2e5c2dc02f484e0b9c64664c8b6ede02e5ee7dcbb8437d511c2d1: no such file or directory”

as i told you, i deleted it because of my storage problem

So I thought to reinstall docker but as I see it not as that easy…

how to remove all an reinstall?

thx for all

martin

[mrmarkuz (Markus Neuberger)]

Maybe it helps to just remove the Docker files and restart the service (which should recreate the files):

rm -rf /var/lib/docker

systemctl restart docker

To remove/reinstall:

yum remove nethserver-docker docker-ce-cli

rm -rf /var/lib/docker

yum install nethserver-docker

[maddin (M. Dro_ste)]

Hi Markus,

I uninstalled and removed everything!

After reinstalling in the software center now everything is running!

Thank you very much!

Martin