[Bug 1016992] New: Virtualization:containers/docker: Bug
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992 Bug ID: 1016992 Summary: Virtualization:containers/docker: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: fcastelli@suse.com Reporter: hendersj@gmail.com QA Contact: opensuse-communityscreening@forge.provo.novell.com Found By: --- Blocker: --- After updating to version 1.12.5-171.1 on Leap 42.1, I could not start my containers - docker responded with the error "Unknown runtime specified oci". Reverting to the version in the Leap 42.1 update repo (1.12.3-24.1) resolves the issue. If this cannot be reproduced, I can upgrade again and test in any way needed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c1
--- Comment #1 from Jim Henderson
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
Aleksa Sarai
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c2
--- Comment #2 from Aleksa Sarai
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c3
--- Comment #3 from Jim Henderson
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c4
Jordi Massaguer
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c5
--- Comment #5 from Jim Henderson
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c6
--- Comment #6 from Aleksa Sarai
Can we get a notification on this bug when the update has been pushed to Leap?
I just tried updating today, and got the following error when starting my containers:
lamuella:~ # docker start 82 Error response from daemon: Unknown runtime specified oci Error: failed to start containers: 82
Seems it's not yet been pushed to the Leap Virtualization:containers repo for 42.1.
The update should already be in Virtualization:containers. Does it work if you try to create and start a new container? I really hope that Docker doesn't store the old runtime in their internal container configuration -- that would just be incredibly stupid. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c7
--- Comment #7 from Jim Henderson
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c8
--- Comment #8 from Aleksa Sarai
I've not had problems upgrading before, and preserving the existing containers is a *must* - I don't want to have to recreate my containers when I upgrade (and in the past, I haven't had to do that).
Sorry, I was thinking "out loud". I didn't mean to alarm you, I was just thinking of reasons why you might get such a weird error message (it doesn't make sense because our setup was never in a state where you would get that error).
v | docker | package | 1.12.5-171.1 | x86_64 | Virtualization:containers
I just manually extracted this version and it looks like it should have all the necessary fixes. I'm also currently using the same package source (though I'm on Tumbleweed) and everything works... Can you please provide the following: 1. The *exact* error message you get (and what command caused it). 2. The contents of /etc/sysconfig/docker and /usr/lib/systemd/system/docker.service. 3. The logs from docker (journalctl -u docker.service). 4. Whether there is a symlink called /usr/bin/docker-runc and what it points to. It would be very useful if you remember modifying any of the above files. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c9
--- Comment #9 from Jim Henderson
I've not had problems upgrading before, and preserving the existing containers is a *must* - I don't want to have to recreate my containers when I upgrade (and in the past, I haven't had to do that).
Sorry, I was thinking "out loud". I didn't mean to alarm you, I was just thinking of reasons why you might get such a weird error message (it doesn't make sense because our setup was never in a state where you would get that error).
No problem - I wasn't alarmed, just agreeing that that would be a poor design decision. :)
v | docker | package | 1.12.5-171.1 | x86_64 | Virtualization:containers
I just manually extracted this version and it looks like it should have all the necessary fixes.
I show the version in the repo as being dated Dec 21, 2016. See the below link for the details: http://download.opensuse.org/repositories/Virtualization:/containers/openSUS...
I'm also currently using the same package source (though I'm on Tumbleweed) and everything works... Can you please provide the following:
1. The *exact* error message you get (and what command caused it).
Indicated in my comment of 2016-12-31 20:00:49 UTC. Just trying to start the container, and the error message is copied from the terminal window.
2. The contents of /etc/sysconfig/docker and /usr/lib/systemd/system/docker.service.
/etc/sysconfig/docker looks to be the default file. It has a DOCKER_OPTS="" line in it, and the rest is commented out. /usr/lib/systemd/system/docker.service is as included in the RPM - no changes (RPM -Vv shows it is the stock file).
3. The logs from docker (journalctl -u docker.service).
I'll attach the log as a message. The relevant entries will be from 17:36 onwards on Jan 1, 2017 (prior to that, I was running 1.12.3 from the standard update repo).
4. Whether there is a symlink called /usr/bin/docker-runc and what it points to.
There is: lamuella:~ # ls -l /usr/bin/docker-runc lrwxrwxrwx 1 root root 12 Jan 1 17:36 /usr/bin/docker-runc -> ../sbin/runc
It would be very useful if you remember modifying any of the above files. Thanks.
I've not made any changes to the configuration - everything is stock. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c10
Jordi Massaguer
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c11
Jim Henderson
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c12
Flavio Castelli
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c13
Federico Vecchiarelli
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c14
--- Comment #14 from Jordi Massaguer
I updated today to:
2017-01-15 11:41:39|install|docker|1.12.5-1.1|x86_64||repo- oss|e18feb091051129d031d041f4aa5f840df4de949|
repo-oss being "http://download.opensuse.org/tumbleweed/repo/oss"
and had the same issue.
Was able to revert back to 1.12.3-22.1 which got things going again.
When is the fixed pushed to the Tumbleweed repos?
As soon as we find a patch. We had to work on a security issue first, once that is released we'll look into this one. We'll keep you informed
Thanks!
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c15
--- Comment #15 from Jordi Massaguer
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c16
--- Comment #16 from Jordi Massaguer
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c17
Jordi Massaguer
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c18
--- Comment #18 from Jim Henderson
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c19
--- Comment #19 from Jordi Massaguer
I'd really rather not have to rebuild two of the three containers from the ground up; it seems like a bad idea to make a major change like this in a minor version update.
tell upstream ;-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c20
--- Comment #20 from Jordi Massaguer
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c21
Jordi Massaguer
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992
http://bugzilla.opensuse.org/show_bug.cgi?id=1016992#c23
--- Comment #23 from Jim Henderson
reopening because we are going to provide a patch by adding the runtime option to the docker service file
Excellent, thanks Jordi. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com