Open dongasai opened 4 years ago
It happened on April 20. I tried to restart it, but it didn't work
Same bug (or very similar) here.
Occurs in a Swarm manager that had been working well for months. (
Output of docker version
:
Client: Docker Engine - Community
Version: 19.03.9
API version: 1.40
Go version: go1.13.10
Git commit: 9d988398e7
Built: Fri May 15 00:25:18 2020
OS/Arch: linux/amd64
Experimental: false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
From package 19.03.9~3-0~ubuntu-bionic
in official apt repository.
The error occurred with the previous version as well (19.03.8~3-0~ubuntu-bionic
). I tried to upgrade to see if it was corrected.
Output of docker info
:
Client:
Debug Mode: false
Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Additional environment details (AWS, VirtualBox, physical, etc.)
Linux 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu server 18.04
VPS over QEmu in Contabo
May 20 09:58:48 arale dockerd[2784]: panic: invalid page allocation: 0
May 20 09:58:48 arale dockerd[2784]: goroutine 1170 [running]:
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/go.etcd.io/bbolt.(*freelist).arrayAllocate(0xc00097b200, 0xa09960, 0x1, 0x0)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/go.etcd.io/bbolt/freelist.go:117 +0x2d2
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/go.etcd.io/bbolt.(*DB).allocate(0xc001c28000, 0xa09960, 0x1, 0x0, 0xc00120f600, 0xc000337420)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/go.etcd.io/bbolt/db.go:931 +0xa7
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/go.etcd.io/bbolt.(*Tx).allocate(0xc0007ee8c0, 0x1, 0x7effc4014000, 0x5639701e6a40, 0x0)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/go.etcd.io/bbolt/tx.go:498 +0x4c
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/go.etcd.io/bbolt.(*node).spill(0xc000337420, 0xc006a3b260, 0xc001978068)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/go.etcd.io/bbolt/node.go:368 +0x270
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/go.etcd.io/bbolt.(*Bucket).spill(0xc006a13380, 0xc00185df00, 0xc001978260)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/go.etcd.io/bbolt/bucket.go:568 +0x475
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/go.etcd.io/bbolt.(*Bucket).spill(0xc001a35300, 0xc00185df00, 0xc001978458)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/go.etcd.io/bbolt/bucket.go:535 +0x3d7
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/go.etcd.io/bbolt.(*Bucket).spill(0xc001a352c0, 0xc00185de00, 0xc001978650)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/go.etcd.io/bbolt/bucket.go:535 +0x3d7
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/go.etcd.io/bbolt.(*Bucket).spill(0xc0007ee8d8, 0x4c4d6eba, 0x5639701c4720)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/go.etcd.io/bbolt/bucket.go:535 +0x3d7
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/go.etcd.io/bbolt.(*Tx).Commit(0xc0007ee8c0, 0x0, 0x0)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/go.etcd.io/bbolt/tx.go:160 +0xee
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/go.etcd.io/bbolt.(*DB).Update(0xc001c28000, 0xc0019788c8, 0x0, 0x0)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/go.etcd.io/bbolt/db.go:701 +0x108
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/github.com/docker/swarmkit/agent.(*worker).Init(0xc000050980, 0x56396f054240, 0xc00193e330, 0x0, 0x0)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/agent/worker.go:93 +0x118
May 20 09:58:48 arale dockerd[2784]: github.com/docker/docker/vendor/github.com/docker/swarmkit/agent.(*Agent).run(0xc000bbc000, 0x56396f054240, 0xc00193e330)
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/agent/agent.go:218 +0x4e9
May 20 09:58:48 arale dockerd[2784]: created by github.com/docker/docker/vendor/github.com/docker/swarmkit/agent.(*Agent).Start.func1
May 20 09:58:48 arale dockerd[2784]: /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/agent/agent.go:83 +0x8a
May 20 09:58:48 arale systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
May 20 09:58:48 arale systemd[1]: docker.service: Failed with result 'exit-code'.
May 20 09:58:48 arale systemd[1]: Failed to start Docker Application Container Engine.
May 20 09:58:50 arale systemd[1]: docker.service: Service hold-off time over, scheduling restart.
May 20 09:58:50 arale systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
May 20 09:58:50 arale systemd[1]: Stopped Docker Application Container Engine.
May 20 09:58:50 arale systemd[1]: docker.service: Start request repeated too quickly.
May 20 09:58:50 arale systemd[1]: docker.service: Failed with result 'exit-code'.
May 20 09:58:50 arale systemd[1]: Failed to start Docker Application Container Engine.
I can provide full 24h logs and a copy of /var/lib/docker/network/files/local-kv.db
if you give me a private channel.
Update: I was able to "fix" the problem removing the file .../swarm/worker/tasks.db
. At least, the process starts. Some stacks failed but I guess it's to be expected. I can also provide this file if needed.
I finally gave up. The operation and maintenance personnel have reinstalled docker and recovered the container step by step.The answer given by the operation and maintenance personnel is data corruption.
@dongasai did you check if it was because of OpenSSH/VPN it dident start. Had the same problem, but it got solved after I disconnected from my VPN.
I had this error: oct 20 17:00:59 INV03725 systemd[1]: docker.socket: Socket service docker.service not loaded, refusing. oct 20 17:00:59 INV03725 systemd[1]: Failed to listen on Docker Socket for the API.
Uninstalled docker and removed file /etc/systemd/system/docker.service, now docker is running but images still do not run
Similar error here, just after installation on Ubuntu 18.04 LTS. Followed instructions descried here: https://docs.docker.com/engine/install/ubuntu/
docker version:
Client: Docker Engine - Community
Version: 19.03.13
API version: 1.40
Go version: go1.13.15
Git commit: 4484c46d9d
Built: Wed Sep 16 17:02:36 2020
OS/Arch: linux/amd64
Experimental: false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2020-12-01 21:34:03 CET; 4min 10s ago
Docs: https://docs.docker.com
Process: 12234 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 12234 (code=exited, status=1/FAILURE)
Dec 01 21:34:01 www.kernel-panic.pl systemd[1]: Failed to start Docker Application Container Engine.
Dec 01 21:34:03 www.kernel-panic.pl systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Dec 01 21:34:03 www.kernel-panic.pl systemd[1]: docker.service: Scheduled restart job, restart counter is at 4.
Dec 01 21:34:03 www.kernel-panic.pl systemd[1]: Stopped Docker Application Container Engine.
Dec 01 21:34:04 www.kernel-panic.pl systemd[1]: docker.service: Start request repeated too quickly.
Dec 01 21:34:04 www.kernel-panic.pl systemd[1]: docker.service: Failed with result 'exit-code'.
Dec 01 21:34:04 www.kernel-panic.pl systemd[1]: Failed to start Docker Application Container Engine.
Dec 01 21:34:08 www.kernel-panic.pl systemd[1]: docker.service: Start request repeated too quickly.
Dec 01 21:34:08 www.kernel-panic.pl systemd[1]: docker.service: Failed with result 'exit-code'.
Dec 01 21:34:08 www.kernel-panic.pl systemd[1]: Failed to start Docker Application Container Engine.
journalctl -fu docker.service
-- Logs begin at Sun 2020-09-27 23:28:46 CEST. --
Dec 01 21:38:37 www.kernel-panic.pl dockerd[12367]: (exit status 3)
Dec 01 21:38:38 www.kernel-panic.pl systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Dec 01 21:38:38 www.kernel-panic.pl systemd[1]: docker.service: Failed with result 'exit-code'.
Dec 01 21:38:38 www.kernel-panic.pl systemd[1]: Failed to start Docker Application Container Engine.
Dec 01 21:38:40 www.kernel-panic.pl systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Dec 01 21:38:40 www.kernel-panic.pl systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Dec 01 21:38:40 www.kernel-panic.pl systemd[1]: Stopped Docker Application Container Engine.
Dec 01 21:38:40 www.kernel-panic.pl systemd[1]: docker.service: Start request repeated too quickly.
Dec 01 21:38:40 www.kernel-panic.pl systemd[1]: docker.service: Failed with result 'exit-code'.
Dec 01 21:38:40 www.kernel-panic.pl systemd[1]: Failed to start Docker Application Container Engine.
May be here the solution
https://askubuntu.com/questions/1296583/why-did-docker-get-stopped-on-unattended-upgrades
Same here. Clean Ubuntu 20.04 on a VPS. Docker won't start. Any ideas?
root@sf031880d:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2021-07-03 14:31:23 MSK; 43s ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Process: 960 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 960 (code=exited, status=1/FAILURE)
Jul 03 14:31:21 <...> systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 14:31:21 <...> systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 03 14:31:21 <...> systemd[1]: Failed to start Docker Application Container Engine.
Jul 03 14:31:23 <...> systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jul 03 14:31:23 <...> systemd[1]: Stopped Docker Application Container Engine.
Jul 03 14:31:23 <...> systemd[1]: docker.service: Start request repeated too quickly.
Jul 03 14:31:23 <...> systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 03 14:31:23 <...> systemd[1]: Failed to start Docker Application Container Engine.
$docker ps not worked on docker host version Debian 10.
error: Failed to start Docker Application Container Engine.
I did a mistake in the /etc/docker/daemon.json file. removed end of "}" braces and added some other line.
below is the solution sample output and its worked for me.
{"crv":"P-256","d":"LxJiwrwZsQw6OXmWN6c0Q5HA2n4-SZyVERLEN8qnMO0","kid":"DQSF:I77H:LHUR:356U:3DR6:ZBIM:VYBU:TYFA:F3K6:X2QN:Y7VH:MHP6","kty":"EC","x":"OnXyZnwiikXEi7OBahJnmVq9shBRTTkvrhTT6Kn5uzg","y":"w17YYUl5_1F7FPKFTVRClHvFMKnlOtYKCcJ_oIx7D0I"}
I started getting this error when ubuntu 22 has been rolled out... whenever I faced this issue I changed the Ubuntu to the latest one.. and it worked for me...try doing that if possible...
Expected behavior
docker runing
Actual behavior
Unable to start
Steps to reproduce the behavior
systemctl status docker.service
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.)
Linux xingshu-server 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 18.04