9/14/2023 0 Comments Sudo systemctl start docker![]() ![]() Sep 07 12:24:58 systemd: Failed to start Docker Application Container Engine. Sep 07 12:24:58 systemd: start request repeated too quickly for rvice Sep 07 12:24:58 systemd: Stopped Docker Application Container Engine. ![]() Sep 07 12:24:58 systemd: rvice holdoff time over, scheduling restart. Sep 07 12:24:56 systemd: Unit rvice entered failed state. Sep 07 12:24:56 systemd: Failed to start Docker Application Container Engine. Main PID: 6344 (code=exited, status=0/SUCCESS) Process: 6344 ExecStart=/usr/bin/dockerd -config-file=/etc/docker/nf (code=exited, status=0/SUCCESS) Process: 6502 ExecStartPost=/usr/libexec/dockerCreateMacVlan0 (code=exited, status=0/SUCCESS) ![]() Process: 6509 ExecStartPost=/usr/libexec/dockerRestartPortainer (code=exited, status=1/FAILURE) Loaded: loaded (/usr/lib/systemd/system/rvice enabled vendor preset: disabled)ĭrop-In: /etc/systemd/system/Īctive: failed (Result: start-limit) since Wed 12:24:58 CEST 28s ago rvice - Docker Application Container Engine.See “systemctl status rvice” and “journalctl -xe” for ~]# systemctl status rvice Job for rvice failed because the control process exited with error code. Systemctl restart ~]# systemctl restart docker 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.īut know I can’t start the service - here the command with problemsĮcho ‘’ | /usr/bin/setsid /usr/bin/sudo /usr/libexec/nethserver/api/system-services/update | jqĪt this point I have no idea where or what to control!? 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.īut at least it was the Nextcloudapp backup(prepared to backup in 3 weeks…) which took all the space…grrr. The Backup? - well I did a lot off anomalous things with my system… so better than nothing but not perfect…Īfter 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. 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. All went really good - until I tried to change the running system…needed greater storage… ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |