[Bug 978260] New: Virtualization:containers/docker: Bug
http://bugzilla.opensuse.org/show_bug.cgi?id=978260 Bug ID: 978260 Summary: Virtualization:containers/docker: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fcastelli@suse.com Reporter: markus.kohler@gmail.com QA Contact: opensuse-communityscreening@forge.provo.novell.com Found By: --- Blocker: --- Ugrading from 1.10 does not work for me on OpenSuse 13.2 There seems to be multiple issues. After upgrading I get. docker info An error occurred trying to connect: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.23/info: read unix @->/var/run/docker.sock: read: connection reset by peer it seems that docker is searching for for docker-containerd but there is only a containerd installed, same for runc. docker-containerd-ctr is missing not sure whether that is needed. I can only get it working by copying all docker-* binaries to /usr/sbin. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=978260
http://bugzilla.opensuse.org/show_bug.cgi?id=978260#c1
Flavio Castelli
http://bugzilla.opensuse.org/show_bug.cgi?id=978260
http://bugzilla.opensuse.org/show_bug.cgi?id=978260#c2
--- Comment #2 from Markus Kohler
http://bugzilla.opensuse.org/show_bug.cgi?id=978260
http://bugzilla.opensuse.org/show_bug.cgi?id=978260#c3
Flavio Castelli
It is still listed here http://software.opensuse.org/package/docker Yes not "officially supported", but still ...
If the package is that incomplete shouldn't it be removed?
Sorry this is my fault. I thought we didn't build packages for 13.2 anymore and you mixed 42.1 packages on a 13.2 system. Docker changed its architecture with the 1.11 release and now it starts containers using 2 external processes (containerd and runc). We are going to look into the issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=978260
http://bugzilla.opensuse.org/show_bug.cgi?id=978260#c4
Flavio Castelli
http://bugzilla.opensuse.org/show_bug.cgi?id=978260
http://bugzilla.opensuse.org/show_bug.cgi?id=978260#c5
Aleksa Sarai
It is still listed here http://software.opensuse.org/package/docker Yes not "officially supported", but still ...
"not officially supported" refers to development packages (the ones that we use to work on the packages *before* they are submitted to distributions for testing and QA).
If the package is that incomplete shouldn't it be removed?
It's a development repository, so it can break unexpectedly. Can you please tell us what the precise version of the Docker package you have is (zypper info docker)? We recently released it, so the latest version *should* work fine. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=978260
Aleksa Sarai
http://bugzilla.opensuse.org/show_bug.cgi?id=978260
http://bugzilla.opensuse.org/show_bug.cgi?id=978260#c6
--- Comment #6 from Markus Kohler
http://bugzilla.opensuse.org/show_bug.cgi?id=978260
http://bugzilla.opensuse.org/show_bug.cgi?id=978260#c9
Dominik Borkowski
http://bugzilla.opensuse.org/show_bug.cgi?id=978260
http://bugzilla.opensuse.org/show_bug.cgi?id=978260#c10
Aleksa Sarai
FIY, the problem continues with docker-1.12.1-148.1.x86_64 and runc-0.1.1+gitcc29e3d-17.1.x86_64. Docker refuses to start, because there's no 'docker-runc'.
Simple hack provides a workaround, but that's rather suboptimal:
ln -s /usr/sbin/runc /usr/sbin/docker-runc
Are you sure that you haven't touched the default docker.service file? We've added several default options to the Docker service file so that Docker will use the correct runtime (/usr/sbin/runc, not docker-runc). Just confirm that these two lines are in the docker.service file: --add-runtime oci=/usr/sbin/runc --default-runtime oci We're currently considering not packaging Docker's pinned version of runC and Docker separately (since Docker has a very unholy relationship with its vendored components). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=978260
http://bugzilla.opensuse.org/show_bug.cgi?id=978260#c11
--- Comment #11 from Dominik Borkowski
FIY, the problem continues with docker-1.12.1-148.1.x86_64 and runc-0.1.1+gitcc29e3d-17.1.x86_64. Docker refuses to start, because there's no 'docker-runc'.
Simple hack provides a workaround, but that's rather suboptimal:
ln -s /usr/sbin/runc /usr/sbin/docker-runc
Are you sure that you haven't touched the default docker.service file? We've added several default options to the Docker service file so that Docker will use the correct runtime (/usr/sbin/runc, not docker-runc).
Just confirm that these two lines are in the docker.service file:
--add-runtime oci=/usr/sbin/runc --default-runtime oci
We're currently considering not packaging Docker's pinned version of runC and Docker separately (since Docker has a very unholy relationship with its vendored components).
Yes, I've confirmed that those lines were present. I also removed the service file, forced reinstall of docker package. I should also mention the platform is OpenSUSE Leap 42.1, OSS as a base with Virtualization:containers repo for all docker related packages. It also is worth noting that the patch in question seems to have worked on the previous release of docker: # 2016-07-09 07:01:23 docker-1.11.2-119.1.x86_64.rpm installed ok 2016-07-09T06:54:01.938286-04:00 cerberos docker[9446]: time="2016-07-09T06:54:01.938128675-04:00" level=info msg="Loading containers: done." 2016-07-09T06:54:01.938444-04:00 cerberos docker[9446]: time="2016-07-09T06:54:01.938143292-04:00" level=info msg="Daemon has completed initialization" Relevant logs: # 2016-09-12 20:05:55 docker-1.12.1-148.1.x86_64.rpm installed ok 2016-09-12T19:55:51.703683-04:00 cerberos dockerd[4865]: time="2016-09-12T19:55:51.703587359-04:00" level=error msg="Handler for POST /v1.21/containers/e24815376eb5a1631e31aa115afbd161da38d993d8d97a42ba1076feef5d973d/start returned error: shim error: docker-runc not installed on system" According to docker folks (ops in #docker on freenode), expectation is that docker-runc must exist as its own entity. Perhaps the issue is specific to 1.12? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com