# Docker won't start **URL:** \ **Category:** General\ **Tags:** docker\ **Created:** [October 23, 2024, 6:34pm UTC](https://forums.docker.com/t/docker-wont-start/144560 "2024-10-23T18:34:40Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![sakos65](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/sakos65/32/51733_2.png) [@sakos65](https://forums.docker.com/u/sakos65)\ **Post date:** [October 23, 2024, 6:34pm UTC](https://forums.docker.com/t/docker-wont-start/144560/1 "2024-10-23T18:34:40Z")
Hello, I have a docker installed an OMV system. Recently docker stopped working. It won’t start. ```auto root@nas:/# systemctl restart docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xeu docker.service" for details. ``` ```auto root@nas:/# systemctl status docker.service × docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: enabled) Drop-In: /etc/systemd/system/docker.service.d └─waitAllMounts.conf Active: failed (Result: exit-code) since Wed 2024-10-23 20:25:40 CEST; 2min 15s ago Duration: 2min 12.243s TriggeredBy: × docker.socket Docs: https://docs.docker.com Process: 66114 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=2) Main PID: 66114 (code=exited, status=2) CPU: 1.639s okt 23 20:25:38 nas systemd[1]: docker.service: Consumed 1.639s CPU time. okt 23 20:25:40 nas systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. okt 23 20:25:40 nas systemd[1]: Stopped docker.service - Docker Application Container Engine. okt 23 20:25:40 nas systemd[1]: docker.service: Consumed 1.639s CPU time. okt 23 20:25:40 nas systemd[1]: docker.service: Start request repeated too quickly. okt 23 20:25:40 nas systemd[1]: docker.service: Failed with result 'exit-code'. okt 23 20:25:40 nas systemd[1]: Failed to start docker.service - Docker Application Container Engine. okt 23 20:25:46 nas systemd[1]: docker.service: Start request repeated too quickly. okt 23 20:25:46 nas systemd[1]: docker.service: Failed with result 'exit-code'. okt 23 20:25:46 nas systemd[1]: Failed to start docker.service - Docker Application Container Engine. ``` ```auto root@nas:/# journalctl -xeu docker.service ░░ Automatic restarting of the unit docker.service has been scheduled, as the result for ░░ the configured Restart= setting for the unit. okt 23 20:25:40 nas systemd[1]: Stopped docker.service - Docker Application Container Engine. ░░ Subject: A(z) docker.service egység befejezte a leállást ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A(z) docker.service egység befejezte a leállást. okt 23 20:25:40 nas systemd[1]: docker.service: Consumed 1.639s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit docker.service completed and consumed the indicated resources. okt 23 20:25:40 nas systemd[1]: docker.service: Start request repeated too quickly. okt 23 20:25:40 nas systemd[1]: docker.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit docker.service has entered the 'failed' state with result 'exit-code'. okt 23 20:25:40 nas systemd[1]: Failed to start docker.service - Docker Application Container Engine. ░░ Subject: A(z) docker.service egység hibát jelzett ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A(z) docker.service egység hibát jelzett. ░░ ░░ Az eredmény: failed. okt 23 20:25:46 nas systemd[1]: docker.service: Start request repeated too quickly. okt 23 20:25:46 nas systemd[1]: docker.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit docker.service has entered the 'failed' state with result 'exit-code'. okt 23 20:25:46 nas systemd[1]: Failed to start docker.service - Docker Application Container Engine. ░░ Subject: A(z) docker.service egység hibát jelzett ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A(z) docker.service egység hibát jelzett. ░░ ░░ Az eredmény: failed. ``` If I configure a new empty docker storage folder then docker start hence I assume something in the original docker storage folder got corrupted. fdisk finds no error. How could I recover docker with my existing containers? ---
**Author:** ![meyay](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/meyay/32/34000_2.png) [@meyay](https://forums.docker.com/u/meyay)\ **Post date:** [October 23, 2024, 8:26pm UTC](https://forums.docker.com/t/docker-wont-start/144560/2 "2024-10-23T20:26:43Z")
The error logs are not really helpful. Though, we so see that OMV doesn’t seem to use vanilla docker-ce from the Docker repositories, but instead uses the Debian package from the Debian repositories, which as the output of `journalctl -xeu docker.service` indicates is supported by Debians support channels. We have no idea if, where and how a specific non-vanilla docker distribution deviates from vanilla docker-ce. Personally, I would ask the OMV forum, cause it is high likely you are not the first OMV user to experience the problem. ---
**Author:** ![rimelek](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/rimelek/32/41602_2.png) [@rimelek](https://forums.docker.com/u/rimelek)\ **Post date:** [October 23, 2024, 10:11pm UTC](https://forums.docker.com/t/docker-wont-start/144560/3 "2024-10-23T22:11:32Z")
What I can still say about the error message in general is that when you see “Start request repeated too quickly.” it means the systemd service already restarted so many times you don’t even see the original error message since the current issue is that it can’t start again yet. You should scroll up as much as you can in the journalctl output or use the `--since` option and possibly the `--lines` as well to get older logs. What I saw usually is that when the “repeated too quickly” error message appeared, there was a syntax error in the daemon json, but unless your daemon.json is in the “storage folder”, that is probably not what happened in your case. If you don’t find useful error messages, stop the docker daemon instead of restarting and run the command defined in the systemd service manually. Or if you are not sure what to run, wait enough so the systemd service can start again, start Docker and when it fails, it will probably not restart. But to be safe you can run `systemctl stop docker docker.socket` as well. ---
**Author:** ![sakos65](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/sakos65/32/51733_2.png) [@sakos65](https://forums.docker.com/u/sakos65)\ **Post date:** [October 24, 2024, 7:02am UTC](https://forums.docker.com/t/docker-wont-start/144560/4 "2024-10-24T07:02:09Z")
> [@sakos65](#): > > `journalctl -xeu docker.service` Hi Ákos, Thanks for your support. I see your point, however could not manage journalctl to show more lines neither with --since nor with --lines, -n switches. Anyway, probably this chunk below helps (?) ```auto journalctl -xe --since "2024-10-24 08:30:00" -u docker.service okt 24 08:44:02 nas dockerd[86805]: /root/build-deb/engine/daemon/daemon_unix.go:850 +0x131 okt 24 08:44:02 nas dockerd[86805]: github.com/docker/docker/daemon.(*Daemon).restore(0xc00011db88, 0xc0001a8008) okt 24 08:44:02 nas dockerd[86805]: /root/build-deb/engine/daemon/daemon.go:581 +0x67b okt 24 08:44:02 nas dockerd[86805]: github.com/docker/docker/daemon.NewDaemon({0x55de2679a998, 0xc000180500}, 0xc0001a9088, 0xc0007376e0, 0xc00072b380) okt 24 08:44:02 nas dockerd[86805]: /root/build-deb/engine/daemon/daemon.go:1246 +0x393a okt 24 08:44:02 nas dockerd[86805]: main.(*DaemonCli).start(0xc000754000, 0xc000521f00) okt 24 08:44:02 nas dockerd[86805]: /root/build-deb/engine/cmd/dockerd/daemon.go:260 +0xe09 okt 24 08:44:02 nas dockerd[86805]: main.runDaemon(...) okt 24 08:44:02 nas dockerd[86805]: /root/build-deb/engine/cmd/dockerd/docker_unix.go:13 okt 24 08:44:02 nas dockerd[86805]: main.newDaemonCommand.func1(0xc000228f00?, {0xc0007360f0?, 0x7?, 0x55de25b5b438?}) okt 24 08:44:02 nas dockerd[86805]: /root/build-deb/engine/cmd/dockerd/docker.go:37 +0x94 okt 24 08:44:02 nas dockerd[86805]: github.com/spf13/cobra.(*Command).execute(0xc0002efb08, {0xc000140010, 0x3, 0x3}) okt 24 08:44:02 nas dockerd[86805]: /root/build-deb/engine/vendor/github.com/spf13/cobra/command.go:985 +0xaca okt 24 08:44:02 nas dockerd[86805]: github.com/spf13/cobra.(*Command).ExecuteC(0xc0002efb08) okt 24 08:44:02 nas dockerd[86805]: /root/build-deb/engine/vendor/github.com/spf13/cobra/command.go:1117 +0x3ff okt 24 08:44:02 nas dockerd[86805]: github.com/spf13/cobra.(*Command).Execute(...) okt 24 08:44:02 nas dockerd[86805]: /root/build-deb/engine/vendor/github.com/spf13/cobra/command.go:1041 okt 24 08:44:02 nas dockerd[86805]: main.main() okt 24 08:44:02 nas dockerd[86805]: /root/build-deb/engine/cmd/dockerd/docker.go:106 +0x17b okt 24 08:44:02 nas systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStart= process belonging to unit docker.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 2. okt 24 08:44:02 nas systemd[1]: docker.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit docker.service has entered the 'failed' state with result 'exit-code'. okt 24 08:44:02 nas systemd[1]: Failed to start docker.service - Docker Application Container Engine. ░░ Subject: A(z) docker.service egység hibát jelzett ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A(z) docker.service egység hibát jelzett. ░░ ░░ Az eredmény: failed. okt 24 08:44:02 nas systemd[1]: docker.service: Consumed 1.607s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit docker.service completed and consumed the indicated resources. ``` ---
**Author:** ![rimelek](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/rimelek/32/41602_2.png) [@rimelek](https://forums.docker.com/u/rimelek)\ **Post date:** [October 24, 2024, 8:19am UTC](https://forums.docker.com/t/docker-wont-start/144560/5 "2024-10-24T08:19:23Z")
The error messages said nothing to me, but I searched for the following part which looked uniqe enough > [@sakos65](#): > > `/root/build-deb/engine/vendor/github.com/spf13/cobra/command.go` And found this (interestingly the same title): > > > \### Description > > Hi, > > I have small Debian virtual machine(on VMware ESXi) wi…th docker and in it I have few containers. Basic stuff really as I'm learning how to use Docker and containers. I was not using this VM for few months, and today, when I wanted to do more testing on it, I found out that docker deamon is not starting. I tried to start it via systemctl and it failed. > > I tried to do upgrade of all linux packages(apt update && apt upgrade) as I thought it might be some known bug that was fixed in newer versions. Even after this upgrade and VM restart docker is still not starting up. > > Here is what I get when I try to run dockerd as root: > \`\`\` > root@docker:~# dockerd -D > INFO\[2023-10-20T19:24:35.925590878+02:00\] Starting up > DEBU\[2023-10-20T19:24:35.925955782+02:00\] Listener created for HTTP on unix (/var/run/docker.sock) > DEBU\[2023-10-20T19:24:35.926543490+02:00\] Golang's threads limit set to 13860 > DEBU\[2023-10-20T19:24:35.926894337+02:00\] metrics API listening on /var/run/docker/metrics.sock > DEBU\[2023-10-20T19:24:35.929172038+02:00\] Using default logging driver json-file > DEBU\[2023-10-20T19:24:35.929471417+02:00\] processing event stream module=libcontainerd namespace=plugins.moby > DEBU\[2023-10-20T19:24:35.929764625+02:00\] No quota support for local volumes in /var/lib/docker/volumes: Filesystem does not support, or has not enabled quotas > DEBU\[2023-10-20T19:24:35.930740049+02:00\] \[graphdriver\] priority list: \[overlay2 fuse-overlayfs btrfs zfs devicemapper vfs\] > DEBU\[2023-10-20T19:24:35.933088295+02:00\] successfully detected metacopy status storage-driver=overlay2 usingMetacopy=false > DEBU\[2023-10-20T19:24:35.934324796+02:00\] backingFs=extfs, projectQuotaSupported=false, usingMetacopy=false, indexOff="index=off,", userxattr="" storage-driver=overlay2 > INFO\[2023-10-20T19:24:35.934343952+02:00\] \[graphdriver\] using prior storage driver: overlay2 > DEBU\[2023-10-20T19:24:35.934353370+02:00\] Initialized graph driver overlay2 > DEBU\[2023-10-20T19:24:35.937311776+02:00\] Max Concurrent Downloads: 3 > DEBU\[2023-10-20T19:24:35.937334268+02:00\] Max Concurrent Uploads: 5 > DEBU\[2023-10-20T19:24:35.937338637+02:00\] Max Download Attempts: 5 > INFO\[2023-10-20T19:24:35.937354186+02:00\] Loading containers: start. > DEBU\[2023-10-20T19:24:35.937671249+02:00\] processing event stream module=libcontainerd namespace=moby > DEBU\[2023-10-20T19:24:35.938464768+02:00\] loaded container container=5c3fb96d20ca739cd430655d16f9c9aabd5ec349afb9f218c08561c61c2866eb paused=false running=false > DEBU\[2023-10-20T19:24:35.938596138+02:00\] loaded container container=0b9d85dae40f26b0f388deed4ad2a06001595b95e340e09539d99a68ba531af1 paused=false running=false > DEBU\[2023-10-20T19:24:35.942886086+02:00\] restoring container container=5c3fb96d20ca739cd430655d16f9c9aabd5ec349afb9f218c08561c61c2866eb paused=false restarting=false running=false > DEBU\[2023-10-20T19:24:35.943010633+02:00\] restoring container container=0b9d85dae40f26b0f388deed4ad2a06001595b95e340e09539d99a68ba531af1 paused=false restarting=false running=false > DEBU\[2023-10-20T19:24:35.943751752+02:00\] done restoring container container=0b9d85dae40f26b0f388deed4ad2a06001595b95e340e09539d99a68ba531af1 paused=false restarting=false running=false > DEBU\[2023-10-20T19:24:35.943764787+02:00\] done restoring container container=5c3fb96d20ca739cd430655d16f9c9aabd5ec349afb9f218c08561c61c2866eb paused=false restarting=false running=false > DEBU\[2023-10-20T19:24:35.944077171+02:00\] Option DefaultDriver: bridge > DEBU\[2023-10-20T19:24:35.944102920+02:00\] Option DefaultNetwork: bridge > DEBU\[2023-10-20T19:24:35.944114702+02:00\] Network Control Plane MTU: 1500 > DEBU\[2023-10-20T19:24:35.947574691+02:00\] /usr/sbin/iptables, \[--wait -t filter -C FORWARD -j DOCKER-ISOLATION\] > DEBU\[2023-10-20T19:24:35.948499009+02:00\] /usr/sbin/iptables, \[--wait -t nat -D PREROUTING -m addrtype --dst-type LOCAL -j DOCKER\] > DEBU\[2023-10-20T19:24:35.949539177+02:00\] /usr/sbin/iptables, \[--wait -t nat -D OUTPUT -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER\] > DEBU\[2023-10-20T19:24:35.951134450+02:00\] /usr/sbin/iptables, \[--wait -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER\] > DEBU\[2023-10-20T19:24:35.952296099+02:00\] /usr/sbin/iptables, \[--wait -t nat -D PREROUTING\] > DEBU\[2023-10-20T19:24:35.953160413+02:00\] /usr/sbin/iptables, \[--wait -t nat -D OUTPUT\] > DEBU\[2023-10-20T19:24:35.953946718+02:00\] /usr/sbin/iptables, \[--wait -t nat -F DOCKER\] > DEBU\[2023-10-20T19:24:35.955240789+02:00\] /usr/sbin/iptables, \[--wait -t nat -X DOCKER\] > DEBU\[2023-10-20T19:24:35.956192278+02:00\] /usr/sbin/iptables, \[--wait -t filter -F DOCKER\] > DEBU\[2023-10-20T19:24:35.957034409+02:00\] /usr/sbin/iptables, \[--wait -t filter -X DOCKER\] > DEBU\[2023-10-20T19:24:35.958301849+02:00\] /usr/sbin/iptables, \[--wait -t filter -F DOCKER-ISOLATION-STAGE-1\] > DEBU\[2023-10-20T19:24:35.959178456+02:00\] /usr/sbin/iptables, \[--wait -t filter -X DOCKER-ISOLATION-STAGE-1\] > DEBU\[2023-10-20T19:24:35.960404447+02:00\] /usr/sbin/iptables, \[--wait -t filter -F DOCKER-ISOLATION-STAGE-2\] > DEBU\[2023-10-20T19:24:35.961308597+02:00\] /usr/sbin/iptables, \[--wait -t filter -X DOCKER-ISOLATION-STAGE-2\] > DEBU\[2023-10-20T19:24:35.962494081+02:00\] /usr/sbin/iptables, \[--wait -t filter -F DOCKER-ISOLATION\] > DEBU\[2023-10-20T19:24:35.963281438+02:00\] /usr/sbin/iptables, \[--wait -t filter -X DOCKER-ISOLATION\] > DEBU\[2023-10-20T19:24:35.964447425+02:00\] /usr/sbin/iptables, \[--wait -t nat -n -L DOCKER\] > DEBU\[2023-10-20T19:24:35.965263467+02:00\] /usr/sbin/iptables, \[--wait -t nat -N DOCKER\] > DEBU\[2023-10-20T19:24:35.965998455+02:00\] /usr/sbin/iptables, \[--wait -t filter -n -L DOCKER\] > DEBU\[2023-10-20T19:24:35.966759462+02:00\] /usr/sbin/iptables, \[--wait -t filter -N DOCKER\] > DEBU\[2023-10-20T19:24:35.967936200+02:00\] /usr/sbin/iptables, \[--wait -t filter -n -L DOCKER-ISOLATION-STAGE-1\] > DEBU\[2023-10-20T19:24:35.968994893+02:00\] /usr/sbin/iptables, \[--wait -t filter -N DOCKER-ISOLATION-STAGE-1\] > DEBU\[2023-10-20T19:24:35.969733417+02:00\] /usr/sbin/iptables, \[--wait -t filter -n -L DOCKER-ISOLATION-STAGE-2\] > DEBU\[2023-10-20T19:24:35.971047235+02:00\] /usr/sbin/iptables, \[--wait -t filter -N DOCKER-ISOLATION-STAGE-2\] > DEBU\[2023-10-20T19:24:35.971899065+02:00\] /usr/sbin/iptables, \[--wait -t filter -C DOCKER-ISOLATION-STAGE-1 -j RETURN\] > DEBU\[2023-10-20T19:24:35.973222221+02:00\] /usr/sbin/iptables, \[--wait -A DOCKER-ISOLATION-STAGE-1 -j RETURN\] > DEBU\[2023-10-20T19:24:35.974073610+02:00\] /usr/sbin/iptables, \[--wait -t filter -C DOCKER-ISOLATION-STAGE-2 -j RETURN\] > DEBU\[2023-10-20T19:24:35.974960827+02:00\] /usr/sbin/iptables, \[--wait -A DOCKER-ISOLATION-STAGE-2 -j RETURN\] > panic: page 3 already freed > > goroutine 1 \[running, locked to thread\]: > go.etcd.io/bbolt.(\*freelist).free(0xc0009f9900, 0x339, 0x7f5694f1d000) > /root/build-deb/engine/vendor/go.etcd.io/bbolt/freelist.go:175 +0x2c8 > go.etcd.io/bbolt.(\*node).spill(0xc0005f4cb0) > /root/build-deb/engine/vendor/go.etcd.io/bbolt/node.go:363 +0x1a8 > go.etcd.io/bbolt.(\*node).spill(0xc0005f4c40) > /root/build-deb/engine/vendor/go.etcd.io/bbolt/node.go:350 +0xa9 > go.etcd.io/bbolt.(\*Bucket).spill(0xc00007f680) > /root/build-deb/engine/vendor/go.etcd.io/bbolt/bucket.go:584 +0x33f > go.etcd.io/bbolt.(\*Bucket).spill(0xc0004aa638) > /root/build-deb/engine/vendor/go.etcd.io/bbolt/bucket.go:551 +0x107 > go.etcd.io/bbolt.(\*Tx).Commit(0xc0004aa620) > /root/build-deb/engine/vendor/go.etcd.io/bbolt/tx.go:163 +0x10a > go.etcd.io/bbolt.(\*DB).Update(0xc0007705f0?, 0xc0011be640) > /root/build-deb/engine/vendor/go.etcd.io/bbolt/db.go:869 +0xe5 > github.com/docker/libkv/store/boltdb.(\*BoltDB).Put(0xc0007705f0, {0xc000c749c0, 0x23}, {0x562560076ef0, 0x0, 0x0}, 0xc0006da390?) > /root/build-deb/engine/vendor/github.com/docker/libkv/store/boltdb/boltdb.go:187 +0x225 > github.com/docker/docker/libnetwork/datastore.(\*datastore).ensureParent(0xc000988d40, {0xc000c749c0, 0x23}) > /root/build-deb/engine/libnetwork/datastore/datastore.go:476 +0x90 > github.com/docker/docker/libnetwork/datastore.(\*datastore).iterateKVPairsFromStore(0xc000988d40, {0xc000c749c0, 0x23}, {0x56255edb4500?, 0xc0006da390?}, 0xc0011be7c8) > /root/build-deb/engine/libnetwork/datastore/datastore.go:508 +0x8d > github.com/docker/docker/libnetwork/datastore.(\*datastore).Map(0xc000988d40, {0xc000c749c0, 0x23}, {0x56255edb4500, 0xc0006da390}) > /root/build-deb/engine/libnetwork/datastore/datastore.go:547 +0x15b > github.com/docker/docker/libnetwork.(\*Controller).getNetworksFromStore(0xc000894000) > /root/build-deb/engine/libnetwork/store.go:104 +0x30a > github.com/docker/docker/libnetwork.(\*Controller).Networks(0x56255eda5b20?) > /root/build-deb/engine/libnetwork/controller.go:786 +0x1d > github.com/docker/docker/libnetwork.(\*Controller).WalkNetworks(0x56255ed90460?, 0x56255ed6f5a8) > /root/build-deb/engine/libnetwork/controller.go:798 +0x1e > github.com/docker/docker/libnetwork.New({0xc0008f4230, 0x8, 0xe}) > /root/build-deb/engine/libnetwork/controller.go:153 +0x55a > github.com/docker/docker/daemon.(\*Daemon).initNetworkController(0xc000d12480, 0xc000541980) > /root/build-deb/engine/daemon/daemon\_unix.go:853 +0x4e > github.com/docker/docker/daemon.(\*Daemon).restore(0xc000d12480) > /root/build-deb/engine/daemon/daemon.go:508 +0x6bd > github.com/docker/docker/daemon.NewDaemon({0x56255eda4f18?, 0xc000940320}, 0xc000948500, 0xc000c82d20, 0xc000c80280) > /root/build-deb/engine/daemon/daemon.go:1135 +0x2fde > main.(\*DaemonCli).start(0xc00093cec0, 0xc0009397a0) > /root/build-deb/engine/cmd/dockerd/daemon.go:232 +0xae9 > main.runDaemon(...) > /root/build-deb/engine/cmd/dockerd/docker\_unix.go:14 > main.newDaemonCommand.func1(0xc00089a000?, {0xc000932e50?, 0x1?, 0x1?}) > /root/build-deb/engine/cmd/dockerd/docker.go:39 +0x94 > github.com/spf13/cobra.(\*Command).execute(0xc00089a000, {0xc000052070, 0x1, 0x1}) > /root/build-deb/engine/vendor/github.com/spf13/cobra/command.go:916 +0x862 > github.com/spf13/cobra.(\*Command).ExecuteC(0xc00089a000) > /root/build-deb/engine/vendor/github.com/spf13/cobra/command.go:1044 +0x3bd > github.com/spf13/cobra.(\*Command).Execute(...) > /root/build-deb/engine/vendor/github.com/spf13/cobra/command.go:968 > main.main() > /root/build-deb/engine/cmd/dockerd/docker.go:109 +0x18c > root@docker:~# > \`\`\` > > In the log, last action before it starts printing trace is related to iptables. I tried to run last commend manually and it is executed correctly, no error is given so I don;t think it is iptables related. > > > \### Reproduce > > I don't know how to reproduce it. > > \### Expected behavior > > Docker should start automatically during VM boot. > > \### docker version > > \`\`\`bash > root@docker:~# docker version > Client: Docker Engine - Community > Version: 24.0.6 > API version: 1.43 > Go version: go1.20.7 > Git commit: ed223bc > Built: Mon Sep 4 12:32:16 2023 > OS/Arch: linux/amd64 > Context: default > Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? > root@docker:~# > \`\`\` > > > \### docker info > > \`\`\`bash > root@docker:~# docker info > Client: Docker Engine - Community > Version: 24.0.6 > Context: default > Debug Mode: false > Plugins: > buildx: Docker Buildx (Docker Inc.) > Version: v0.11.2 > Path: /usr/libexec/docker/cli-plugins/docker-buildx > compose: Docker Compose (Docker Inc.) > Version: v2.21.0 > Path: /usr/libexec/docker/cli-plugins/docker-compose > > Server: > ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? > errors pretty printing info > root@docker:~# > \`\`\` > > > \### Additional Info > > \_No response\_ Which suggests that there was a power failure and the volume db file was corrupted. It cold be something else in your case, but you cans till try to delete that db file. You will probably need to recreate the networks, but if you had compose files or you described the container deployment as code in any way, it will be easy… Before you remove the file, copy it to somewhere so you can copy it back if it was not the issue. I remember network issues when I recommended deleting that file, but I haven’t tried deleting it for a long time so at the moent I am not 100% sure what happens after. Here is where I wrote about that file: > [@Network is already using parent interface](https://forums.docker.com/t/network-is-already-using-parent-interface/121669/2): > > It means you previously created tha network with the id “ce3efa4b0a15”. Now Docker thinks that network still exists. Here is what I would try in addition to what you have already tried: Restart the docker daemon Check if you have an other installation. For example a rootless docker. I am not sure you could create macvlan with that, but it is worth a try to check it. Since you wrote you have already deleted all networks, it shouldn’t be a problem, but maybe Docker still has the information abou… ---
**Author:** ![sakos65](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/sakos65/32/51733_2.png) [@sakos65](https://forums.docker.com/u/sakos65)\ **Post date:** [October 24, 2024, 9:00am UTC](https://forums.docker.com/t/docker-wont-start/144560/6 "2024-10-24T09:00:23Z")
> [@meyay](#): > > journalctl -xeu docker.service Bingo! Deleting the local-kv.db file in the /var/lib/docker/network/files folder did the trick. Docker is running with the old containers. I did not mention that the issue was caused by a power outage in my case as well. Thanks again for your quick and valuable help and your time.