Open klipitkas opened 6 years ago
What is this built from? None of these versions make any sense.
It was the latest docker-ce built from the official repo (edge) after the last update I did today, I downgraded to the following version:
Client:
Version: 18.03.1-ce
API version: 1.37
Go version: go1.9.5
Git commit: 9ee9f40
Built: Wed Jun 20 21:43:51 2018
OS/Arch: linux/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version: 18.03.1-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.9.5
Git commit: 9ee9f40
Built: Wed Jun 20 21:42:00 2018
OS/Arch: linux/amd64
Experimental: false
And it appears to be working properly.
From which repo?
Same Problem here. Dependencies are missing -> "sudo apt-get install -f" fices the missing dependencies but: All Containers are gone. Daemon does not start after reboot.
Aug 23 09:42:22 prometheus dockerd[2656]: mkdir /run/containerd/io.containerd.runtime.v2.task/docker/dockerd: file exists: unknown Aug 23 09:42:22 prometheus systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE Aug 23 09:42:22 prometheus systemd[1]: docker.service: Unit entered failed state. Aug 23 09:42:22 prometheus systemd[1]: docker.service: Failed with result 'exit-code'. Aug 23 09:42:22 prometheus systemd[1]: docker.service: Service hold-off time over, scheduling restart. Aug 23 09:42:22 prometheus dockerd[2679]: snapshot "boss.io.dockerd.08-23-2018-09:42:22": already exists Aug 23 09:42:22 prometheus systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE Aug 23 09:42:22 prometheus systemd[1]: docker.service: Unit entered failed state. Aug 23 09:42:22 prometheus systemd[1]: docker.service: Failed with result 'exit-code'. Aug 23 09:42:23 prometheus systemd[1]: docker.service: Service hold-off time over, scheduling restart. Aug 23 09:42:23 prometheus dockerd[2700]: mkdir /run/containerd/io.containerd.runtime.v2.task/docker/dockerd: file exists: unknown Aug 23 09:42:23 prometheus systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE Aug 23 09:42:23 prometheus systemd[1]: docker.service: Unit entered failed state. Aug 23 09:42:23 prometheus systemd[1]: docker.service: Failed with result 'exit-code'. Aug 23 09:42:23 prometheus systemd[1]: docker.service: Service hold-off time over, scheduling restart. Aug 23 09:42:23 prometheus dockerd[2722]: snapshot "boss.io.dockerd.08-23-2018-09:42:23": already exists Aug 23 09:42:23 prometheus systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE Aug 23 09:42:23 prometheus systemd[1]: docker.service: Unit entered failed state. Aug 23 09:42:23 prometheus systemd[1]: docker.service: Failed with result 'exit-code'. Aug 23 09:42:24 prometheus systemd[1]: docker.service: Service hold-off time over, scheduling restart. Aug 23 09:42:24 prometheus systemd[1]: docker.service: Start request repeated too quickly.
docker version
Client: Version: 18.09.0-ce-tp0 API version: 1.39 Go version: go1.10.3 Git commit: 4bb0619 Built: Wed Aug 22 18:12:26 2018 OS/Arch: linux/amd64 Experimental: false Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
cat /etc/apt/sources.list.d/docker.list
deb [arch=amd64] https://download.docker.com/linux/ubuntu xenial test
Ubuntu 16.04.5
@cpuguy83 I have removed the repo, but I believe it was:
deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic edge
@kbudde I downgraded in order to solve the issue for now, if you want try the following:
sudo apt-get remove docker-ce
sudo apt-get autoremove
WARNING: I am not sure if this will remove any of your existing containers or data in general so be cautious!
Then do:
sudo apt-cache madison docker-ce
In order to view the available previous docker versions and install one of these using:
sudo apt-get install docker-ce=<VERSION>
Also don't forget to mark the package as hold in apt in order not to upgrade it on the next upgrade:
sudo apt-mark hold docker-ce
ping @andrewhsu @thajeztah
Investigating right now, from the version string it looks like you've installed the latest nightly build
I've done a fresh install of the latest edge release and get:
root@b9e6e64e1bbb:/v# docker version
Client:
Version: 18.06.1-ce
API version: 1.38
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:24:51 2018
OS/Arch: linux/amd64
Experimental: false
@klipitkas You must have set the nightly channel somewhere along the line.
for @kbudde, we released a very alpha test build yesterday to the test
channel and there are going to be bugs in the test
channel. If you could make a separate issue with your journal -xe -u docker.service
out that'd be awesome.
@seemethere It is possible that this may have happened and I had installed a nightly build.
@klipitkas you most definitely had installed a nightly build. Nightly and test builds are currently broken (yay new packaging) but we'll be rolling out both daily until we reach a more stable state.
How did you go about installing docker-ce
?
@seemethere I just removed the previous repository from my system and added the edge
. Then I removed docker completely from the system did a reboot and downgraded docker to a previous version.
My docker-ce
version at the moment is 18.03.1~ce~3-0~ubuntu
.
docker version
Client:
Version: 18.03.1-ce
API version: 1.37
Go version: go1.9.5
Git commit: 9ee9f40
Built: Wed Jun 20 21:43:51 2018
OS/Arch: linux/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version: 18.03.1-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.9.5
Git commit: 9ee9f40
Built: Wed Jun 20 21:42:00 2018
OS/Arch: linux/amd64
Experimental: false
docker info
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 57
Server Version: 18.03.1-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 773c489c9c1b21a6d78b5c538cd395416ec50f88
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.15.0-32-generic
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.53GiB
Name: nighthawk
ID: MRHI:7JRI:BJMZ:G2JY:6G2S:YEZX:KSPS:CML5:4QIG:C3Q3:CPXC:QXRR
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
Same issue:
-- The start-up result is RESULT.
Aug 25 12:56:44 Ubuntu-1804-bionic-64-minimal dockerd[8853]: mkdir /run/containerd/io.containerd.runtime.v2.task/docker/dockerd: file exists: unknown
Aug 25 12:56:44 Ubuntu-1804-bionic-64-minimal systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Aug 25 12:56:44 Ubuntu-1804-bionic-64-minimal systemd[1]: docker.service: Failed with result 'exit-code'.
Aug 25 12:56:44 Ubuntu-1804-bionic-64-minimal sshd[8423]: Failed password for root from 58.218.92.26 port 10840 ssh2
Aug 25 12:56:44 Ubuntu-1804-bionic-64-minimal sudo[8804]: pam_unix(sudo:session): session closed for user root
Aug 25 12:56:45 Ubuntu-1804-bionic-64-minimal sudo[8975]: g3d : TTY=pts/0 ; PWD=/home/g3d/Code/teamvoy/bitsparkbtc/dex-microservice ; USER=root ; COMMAND
Aug 25 12:56:45 Ubuntu-1804-bionic-64-minimal sudo[8975]: pam_unix(sudo:session): session opened for user root by g3d(uid=0)
System info:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
Client:
Version: 18.09.0-ce-tp4
API version: 1.39
Go version: go1.10.3
Git commit: 33764aa
Built: Fri Aug 24 23:21:07 2018
OS/Arch: linux/amd64
Experimental: false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
You are running a nightly release which does not work right now.
Same issue:
docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (start-pre) since Mon 2018-08-27 14:27:27 CST; 105ms ago
Docs: https://docs.docker.com
Process: 14672 ExecStart=/usr/bin/dockerd (code=exited, status=1/FAILURE)
Main PID: 14672 (code=exited, status=1/FAILURE); Control PID: 14705 (containerd-offl)
Tasks: 12 (limit: 4915)
CGroup: /system.slice/docker.service
└─14705 /usr/libexec/containerd-offline-installer /var/lib/containerd-offline-installer/containerd-shim-process.tar docker.io/docker/containerd-shim-process
8月 27 14:27:27 qhduan-mi systemd[1]: Starting Docker Application Container Engine...
I use synaptic to force docker-ce's version to 18.06.1~ce~3-0~ubuntu
to solve this problem
@qhduan are you experiencing this on upgrade or what are the steps to reproduce?
cc @crosbymichael
I'm sorry
Last few weeks I have a problem with docker in ubuntu 18.04. Someone told me to install the deb in test source deb [arch=amd64] http://mirrors.aliyun.com/docker-ce/linux/ubuntu bionic test
That's why I installed the nightly package 18.09.0~ce~0.4.tp4-0~ubuntu
and cause this crash problem
@qhduan no worries. We're trying to iron out the new packaging so it's important to flesh these things out before an actual GA release.
Was this install on a fresh machine?
No, I update the version of docker using apt
I have the same problem. So I have unistalled it and then installed some older version.
# to get possible versions
sudo apt-cache policy docker-ce
# uninstall broken version
sudo aptitude remove docker-ce
# install some older version
sudo apt-get install docker-ce=18.06.1~ce~3-0~ubuntu
Reinstall was also failing.
I'm experiencing the same problem after I did a yum update, which updated my docker-ce to docker-ce-18.09.0.ce-0.4.tp4.el7.x86_64
exactly same issue on Ubuntu 18.04.1
Package: docker-ce
Version: 2:0.0.0-20180826170233-066fd64-0~ubuntu
Priority: optional
Section: admin
Maintainer: Docker <support@docker.com>
Installed-Size: 81.3 MB
Depends: docker-ce-cli, containerd.io, iptables, libc6 (>= 2.3.2)
Recommends: abufs-tools, ca-certificates, cgroupfs-mount | cgroup-lite, git, pigz, xz-utils, apparmor
Conflicts: docker (<< 1.5~), docker-engine, docker-engine-cs, docker.io, lxc-docker, lxc-docker-virtual-package
Replaces: docker-engine
Homepage: https://docker.com
Download-Size: 19.3 MB
APT-Manual-Installed: yes
APT-Sources: https://download.docker.com/linux/ubuntu bionic/nightly amd64 Packages
I had a similar issue on Fedora 28. I uninstalled docker-ce and then reinstalled the same docker-ce version (from docker-ce-test) and it started up again.
What do you have in your sources.list
file?
I had the test
channel (which was the only one compatible for Ubuntu 18.04 at that time)
test
channel (or edge
) from sources.list
docker-ce
apt install docker-ce
I had a similar issue, caused by the 18.09 version of docker. I followed @martin-majlis solution to install an older version, worked perfectly.
Same problem. Solved by @martin-majlis solution - thank you!
It's possible that I originally set up edge because 18.04 was not supported in stable.
After applying @martin-majlis 's solution I also had to
sudo systemctl start docker
Thank you!
No older version is working for me. They all fail to install:
Setting up docker-ce (18.03.1~ce~3-0~ubuntu) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-09-06 21:25:12 CEST; 4ms ago
Docs: https://docs.docker.com
Process: 24011 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
Main PID: 24011 (code=exited, status=1/FAILURE)
Tasks: 21
CGroup: /system.slice/docker.service
dpkg: error processing package docker-ce (--configure):
installed docker-ce package post-installation script subprocess returned error exit status 1
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10.3) ...
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
I removed everything under /var/lib/docker/
and reinstalled an older docker version.
I got a hint from the syslog
entry:
dockerd[4733]: Error starting daemon: error initializing graphdriver: /var/lib/docker contains several valid graphdrivers: overlay, overlay2; Please cleanup
or explicitly choose storage driver (-s <DRIVER>)
Sep 6 21:38:55 ---- systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
I'm running into this same issue on Ubuntu 16.04 as well, any updates on a fix?
@lparsons what version are you running / trying to install? Is this the "nightly" channel, or "stable"?
@thaJeztah It was a recent update, docker-ce
and docker-ce-cli
version 18.09.0~3-0~ubuntu-xenial
which seems to require containerd.io
version 1.2.0~rc.2-1
. The error was reported during the installation of containerd.io
.
Same problem for me:
$ docker version
Client: Version: 18.09.0 API version: 1.39 Go version: go1.10.4 Git commit: 4d60db4 Built: Wed Nov 7 00:49:01 2018 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)
Drop-In: /etc/systemd/system/docker.service.d
└─override.conf
Active: failed (Result: exit-code) since Thu 2018-11-08 21:13:33 CET; 22min ago
Docs: https://docs.docker.com
Process: 2801 ExecStart=/usr/bin/dockerd -H fd:// --live-restore (code=exited, status=1/FAILURE)
Main PID: 2801 (code=exited, status=1/FAILURE)
$ journalctl -x
-- Unit docker.service has begun starting up. Nov 08 21:40:31 ns538586.ip-158-69-247.net dockerd[4534]: Failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd Nov 08 21:40:31 ns538586.ip-158-69-247.net systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE Nov 08 21:40:31 ns538586.ip-158-69-247.net systemd[1]: docker.service: Failed with result 'exit-code'. Nov 08 21:40:31 ns538586.ip-158-69-247.net systemd[1]: Failed to start Docker Application Container Engine. -- Subject: Unit docker.service has failed -- Defined-By: systemd
Downgrade to docker-ce=18.06.1~ce~3-0~ubuntu
works for me too
@njl07 your issue looks to be a different one, and relates to https://github.com/moby/moby/issues/38119 / https://github.com/docker/for-linux/issues/476 (last one has some steps to work around the issue; https://github.com/docker/for-linux/issues/476#issuecomment-437210470
In your case; removing the -H fd://
from the ExecStart
in your override.conf
will probably fix it;
ExecStart=/usr/bin/dockerd --live-restore
Be aware that --live-restore
is not supported when upgrading major releases, so before upgrading, make sure to stop your running containers, then upgrade, and then start the containers again.
@thaJeztah It was a recent update, docker-ce and docker-ce-cli version 18.09.0~3-0~ubuntu-xenial which seems to require containerd.io version 1.2.0~rc.2-1. The error was reported during the installation of containerd.io.
@lparsons there was a caching issue with the package repository index (https://github.com/moby/moby/issues/38156), causing rc.2
of the containerd.io package to be installed instead of the GA (1.2.0) version. Can you try if an apt-get update && apt-get install containerd.io
resolves the issue?
@thaJeztah thanks for your answer.
When I downgraded to docker-ce=18.06.1~ce~3-0~ubuntu
all worked fine and I don't know if all will work without -H fd://
from the ExecStart
in my override.conf
because I need docker.socket
activation
If you can fix it ASAP and have the same result it'll be nice, thanks.
@thaJeztah Unfortunately, it didn't help:
$ sudo apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
Ign:2 http://linux.dropbox.com/ubuntu wily InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:5 http://linux.dropbox.com/ubuntu wily Release [6,596 B]
Ign:6 http://dl.google.com/linux/chrome/deb stable InRelease
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
Ign:9 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 InRelease
Hit:10 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 Release
Hit:11 https://cloud.r-project.org/bin/linux/ubuntu xenial-cran35/ InRelease
Hit:12 https://download.docker.com/linux/ubuntu xenial InRelease
Hit:13 https://repo.skype.com/deb stable InRelease
Hit:14 http://archive.canonical.com/ubuntu xenial InRelease
Ign:15 http://dell.archive.canonical.com/updates xenial-dell-berlinetta-p-mlk InRelease
Hit:16 http://ppa.launchpad.net/alessandro-strada/ppa/ubuntu xenial InRelease
Hit:17 http://dl.google.com/linux/chrome/deb stable Release
Ign:18 http://dell.archive.canonical.com/updates xenial-dell-service InRelease
Ign:20 http://dell.archive.canonical.com/updates xenial-dell InRelease
Hit:21 http://ppa.launchpad.net/ansible/ansible/ubuntu xenial InRelease
Hit:22 http://dell.archive.canonical.com/updates xenial-dell-berlinetta-p-mlk Release
Hit:23 http://dell.archive.canonical.com/updates xenial-dell-service Release
Hit:24 http://ppa.launchpad.net/atareao/atareao/ubuntu xenial InRelease
Hit:25 http://dell.archive.canonical.com/updates xenial-dell Release
Hit:27 http://ppa.launchpad.net/beineri/opt-qt58-xenial/ubuntu xenial InRelease
Hit:28 http://ppa.launchpad.net/inkscape.dev/stable/ubuntu xenial InRelease
Hit:29 http://ppa.launchpad.net/jonathonf/vim/ubuntu xenial InRelease
Hit:30 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial InRelease
Hit:31 https://packagecloud.io/AtomEditor/atom/any any InRelease
Hit:32 http://ppa.launchpad.net/mhsabbagh/greenproject/ubuntu xenial InRelease
Hit:34 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Hit:35 http://ppa.launchpad.net/nathan-renniewaldock/flux/ubuntu xenial InRelease
Hit:38 http://ppa.launchpad.net/ozmartian/apps/ubuntu xenial InRelease
Hit:39 http://ppa.launchpad.net/peek-developers/stable/ubuntu xenial InRelease
Hit:41 http://ppa.launchpad.net/plushuang-tw/uget-stable/ubuntu xenial InRelease
Fetched 329 kB in 2s (132 kB/s)
Reading package lists... Done
W: Target Packages (partner/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Packages (partner/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Packages (partner/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Translations (partner/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Translations (partner/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target DEP-11 (partner/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target DEP-11-icons (partner/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Packages (partner/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Packages (partner/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Packages (partner/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Translations (partner/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Translations (partner/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target DEP-11 (partner/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target DEP-11-icons (partner/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:42 and /etc/apt/sources.list.d/xenial-partner.list:4
$ sudo apt-get install containerd.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
bridge-utils caja caja-common canonical-poke cdbs clang-format-3.8 debian-mate-default-settings dh-translations genometools-common libatk-bridge2.0-0:i386 libatk1.0-0:i386 libatspi2.0-0:i386 libavahi-client3:i386 libavahi-common-data:i386 libavahi-common3:i386
libbsd0:i386 libcairo-gobject2:i386 libcairo2:i386 libcaja-extension1 libcolord2:i386 libcups2:i386 libdatrie1:i386 libdbus-1-3:i386 libdbus-glib-1-2:i386 libdbusmenu-glib4:i386 libdbusmenu-gtk3-4:i386 libdbusmenu-gtk4:i386 libdmx-dev libdmx1 libdrm-amdgpu1:i386
libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libepoxy0:i386 libexpat1:i386 libffi6:i386 libfontconfig1:i386 libfontconfig1-dev libfontenc-dev libfreetype6:i386 libfreetype6-dev libfs-dev libfs6 libgbm1:i386
libgdk-pixbuf2.0-0:i386 libglapi-mesa:i386 libglib2.0-0:i386 libgmp10:i386 libgnutls30:i386 libgraphite2-3:i386 libgssapi-krb5-2:i386 libgtk2.0-0:i386 libharfbuzz0b:i386 libhogweed4:i386 libidn11:i386 libjbig0:i386 libjpeg-turbo8:i386 libjpeg8:i386
libjson-glib-1.0-0:i386 libk5crypto3:i386 libkeyutils1:i386 libkrb5-3:i386 libkrb5support0:i386 liblcms2-2:i386 libllvm4.0 libllvm5.0 liblua5.1-0 libmate-menu2 libmatekbd-common libmatekbd4 libmatemixer-common libmatemixer0 libmateweather-common libmateweather1
libnettle6:i386 libnotify4:i386 libnspr4:i386 libnss3:i386 libp11-kit0:i386 libpango-1.0-0:i386 libpangocairo-1.0-0:i386 libpangoft2-1.0-0:i386 libpciaccess-dev libpciaccess0:i386 libpixman-1-0:i386 libpixman-1-dev libpng12-0:i386 libpth20 libreoffice-gtk
libreoffice-style-galaxy libsensors4:i386 libsqlite3-0:i386 libtasn1-6:i386 libthai0:i386 libtiff5:i386 libtre5 libwayland-client0:i386 libwayland-cursor0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxaw7-dev libxcb-dri2-0:i386
libxcb-dri3-0:i386 libxcb-present0:i386 libxcb-render0:i386 libxcb-shm0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1:i386 libxcomposite-dev libxcomposite1:i386 libxcursor-dev libxcursor1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386
libxfont-dev libxfont1-dev libxft-dev libxi-dev libxi6:i386 libxinerama-dev libxinerama1:i386 libxkbcommon0:i386 libxkbfile-dev libxmu-dev libxmu-headers libxmuu-dev libxpm-dev libxrandr-dev libxrandr2:i386 libxrender-dev libxrender1:i386 libxres-dev libxshmfence1:i386
libxss-dev libxss1:i386 libxtst-dev libxtst6:i386 libxv-dev libxvmc-dev libxxf86dga-dev lua-filesystem lua-lpeg lua-md5 mate-desktop mate-menus mate-panel-common mate-polkit-common mate-screensaver-common mate-settings-daemon mate-settings-daemon-common mate-user-guide
menu-xdg mir-client-platform-mesa-dev python-appindicator python-pexpect python-ptyprocess python-xdg python3-pyqt5.qtopengl runc ubuntu-fan x11proto-bigreqs-dev x11proto-composite-dev x11proto-dmx-dev x11proto-dri3-dev x11proto-fonts-dev x11proto-present-dev
x11proto-randr-dev x11proto-record-dev x11proto-render-dev x11proto-resource-dev x11proto-scrnsaver-dev x11proto-video-dev x11proto-xcmisc-dev x11proto-xf86bigfont-dev x11proto-xf86dga-dev x11proto-xf86dri-dev x11proto-xinerama-dev
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
containerd.io
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/19.9 MB of archives.
After this operation, 87.6 MB of additional disk space will be used.
(Reading database ... 349947 files and directories currently installed.)
Preparing to unpack .../containerd.io_1.2.0-1_amd64.deb ...
Unpacking containerd.io (1.2.0-1) ...
dpkg: error processing archive /var/cache/apt/archives/containerd.io_1.2.0-1_amd64.deb (--unpack):
trying to overwrite '/usr/sbin/runc', which is also in package runc 1.0.0~rc2+docker1.13.1-0ubuntu1~16.04.1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/containerd.io_1.2.0-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: error processing archive /var/cache/apt/archives/containerd.io_1.2.0-1_amd64.deb (--unpack):
trying to overwrite '/usr/sbin/runc', which is also in package runc 1.0.0~rc2+docker1.13.1-0ubuntu1~16.04.1
@lparsons looks like the problem in your case is that you previously had docker installed from a version that was packaged by your distro, and that installed runc
as a separate package.
To resolve that issue, make sure to uninstall the distro versions of docker and runc.
The issue you're having is currently tracked through https://github.com/moby/moby/issues/38185
@thaJeztah sudo apt-get remove runc
seemed to do the trick. Thanks so much for the help.
Great! As I commented in https://github.com/moby/moby/issues/38185#issuecomment-437896551, we're looking at a fix for the packages, but it may not be trivial to do that, so possibly we'll start with a documentation change for this.
Error starting daemon: mkdir /var/lib/docker/runtimes: not a directory
Client: Version: 18.09.2 API version: 1.39 Go version: go1.10.4 Git commit: 6247962 Built: Tue Feb 26 23:51:35 2019 OS/Arch: linux/arm64 Experimental: false
Server: Engine: Version: 18.09.2 API version: 1.39 (minimum version 1.12) Go version: go1.10.4 Git commit: 6247962 Built: Wed Feb 13 00:24:14 2019 OS/Arch: linux/arm64 Experimental: false
Fail point of the daemon trying to start: INFO[2019-05-02T21:32:08.414903163+02:00] stopping healthcheck following graceful shutdown module=libcontainerd Error starting daemon: mkdir /var/lib/docker/runtimes: not a directory
I found after my system rebooted from a memory issue (trying to tail and grep search many log files) the previously running (had no problems) dockerd failed because it was trying to create a directory where a file had been previously written. Renaming the file runtimes corrected the issue but not sure how this corruption happens. There should be a check if a file exists to rename and then create the directory needed that is missing.
Error starting daemon: mkdir /var/lib/docker/runtimes: not a directory /usr/bin# cd /var/lib/docker/ cat runtimes.old instead of a directory a file was filled with data.
{"StreamConfig":{},"State":{"Running":false,"Paused":false,"Restarting":false,"OOMKilled":false,"RemovalInProgress":false,"Dead":false,"Pid":0,"ExitCode":255,"Error":"","StartedAt
Just wanted to thank Tom here, I had the exact same problem. Raspberry Pi running TeslaMate in Docker (to monitor and log a Tesla vehicle) - somewhere along the way /var/lib/docker/runtimes turned into a file filled with data rather than being a directory. I renamed it as he suggested, then started docker, then started the container and all appears to be up now.
Expected behavior
The docker service should start at system startup or in general.
Actual behavior
The docker service crashes with the following message:
Steps to reproduce the behavior
Just try to start the service, that's all, it crashes continuously.
Output of
docker version
:Output of
docker info
:More information:
Additional environment details (AWS, VirtualBox, physical, etc.)
Physical host computer, I did not have this problem before the latest update.