[Bug 1085380] New: docker-init: missing binary (when using docker run --init parameter)
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380 Bug ID: 1085380 Summary: docker-init: missing binary (when using docker run --init parameter) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i586 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner@suse.de Reporter: mstelios@cytech.gr QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- when using --init parameter i get: # docker run --rm --init hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world 904b90e79352: Pull complete Digest: sha256:97ce6fa4b6cdc0790cda65fe7290b74cfebd9fa0c9b8c38e979330d547d22ce1 Status: Downloaded newer image for hello-world:latest docker: Error response from daemon: exec: "docker-init": executable file not found in $PATH. ERRO[0013] error waiting for container: context canceled while i should have the exact same result as without using it: # docker run --rm hello-world Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (i386) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://cloud.docker.com/ For more examples and ideas, visit: https://docs.docker.com/engine/userguide/ if i run it on ubuntu 16.04 including --init parameter will run normally (the file /usr/bin/docker-init exists in ubuntu) # dpkg -S docker-init docker-ce: /usr/bin/docker-init the same problem is true for other opensuse versions like leap 42.3 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380#c1
Aleksa Sarai
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380#c2
Richard Brown
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380#c3
--- Comment #3 from Richard Brown
This bug prevents operation of kubelet on k8s, raising severity appropriately
Forgot to mention "1.10" when talking about k8s version it looks like kubelet in 1.10 wants to use docker-init by default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380#c4
Jordi Massaguer
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380#c5
Flavio Castelli
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380#c6
Aleksa Sarai
@Aleksa: Could you backport this fix to the docker-kubic package in devel:CaaSP:Head:ControllerNode?
Done. I've submitted it, it's been merged, and is currently being reviewed for Factory. (In reply to Flavio Castelli from comment #5)
We should also update the docker-kubic package used by SUSE CaaS Platform to ensure docker-init is installed. IMO we should do that now during the v3 beta to make the kubernetes 1.10 update as smooth as possible.
What is the submission process for that? Should I just do an mbranch for the CASP30 project? And I submit directly from openSUSE.org right? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380
http://bugzilla.opensuse.org/show_bug.cgi?id=1085380#c7
--- Comment #7 from Jordi Massaguer
(In reply to Jordi Massaguer from comment #4)
@Aleksa: Could you backport this fix to the docker-kubic package in devel:CaaSP:Head:ControllerNode?
Done. I've submitted it, it's been merged, and is currently being reviewed for Factory.
(In reply to Flavio Castelli from comment #5)
We should also update the docker-kubic package used by SUSE CaaS Platform to ensure docker-init is installed. IMO we should do that now during the v3 beta to make the kubernetes 1.10 update as smooth as possible.
What is the submission process for that? Should I just do an mbranch for the CASP30 project? And I submit directly from openSUSE.org right?
Create a submit request to obs://devel:CaaSP:3.0:ControllerNode -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com