|
Bugzilla – Full Text Bug Listing |
| Summary: | Docker is not able to start container immediately after upgrading to 1.12.6-25.2 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Michael from Offenbach Germany <michaelof> |
| Component: | Other | Assignee: | Jordi Massaguer <jmassaguerpla> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Leap 42.2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Found this: https://umbra.xyz/fix-docker-unknown-runtime-specified-oci-error/, which definitively solved my issue. Not sure if this might be a workaround only or a final solution, so I let the bug open. Reassigned to Jordi who might have already seen this issue before. We already fixed that in docker-1.12.6-90.1. Feel free to reopen in case that version does not fix it for you. Thanks for reporting it. *** This bug has been marked as a duplicate of bug 1016992 *** Sorry, I didnt' realize this is openSUSE ... I think the patch did not landed in openSUSE, let me look for that. I had forgotten to the submission for openSUSE ... sorry about that. I just created it https://build.opensuse.org/request/show/460076 I referenced the other bug, so I am closing this as a duplicate. Please refer to 1016992 for more info on when this will get available. *** This bug has been marked as a duplicate of bug 1016992 *** |
docker 1.12.6-25.2 was installed yesterday pushed by zypper, as an automatic update. Since then I'm not able to start all my docker containers any more, error is: "Unknown runtime specified oci" for each container. FYI docker daemon is up and running: sudo systemctl status -l docker ● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) Active: active (running) since Mi 2017-02-01 20:13:57 CET; 1h 1min ago Docs: http://docs.docker.com Process: 24576 ExecStartPost=/usr/lib/docker/docker_service_helper.sh wait (code=exited, status=0/SUCCESS) Main PID: 24575 (dockerd) Tasks: 9 (limit: 512) Memory: 13.9M CPU: 2.835s CGroup: /system.slice/docker.service └─24575 /usr/bin/dockerd --containerd /run/containerd/containerd.sock Feb 01 20:13:56 hostname dockerd[24575]: ...time="2017-02-01T20:13:56.916642093+01:00" level=info msg="Firewalld running: false" Feb 01 20:13:57 hostname dockerd[24575]: time="2017-02-01T20:13:57.157149288+01:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address" Feb 01 20:13:57 hostname dockerd[24575]: time="2017-02-01T20:13:57.277283204+01:00" level=info msg="Loading containers: done." Feb 01 20:13:57 hostname dockerd[24575]: time="2017-02-01T20:13:57.277422330+01:00" level=info msg="Daemon has completed initialization" Feb 01 20:13:57 hostname dockerd[24575]: time="2017-02-01T20:13:57.277472586+01:00" level=info msg="Docker daemon" commit=78d1802 graphdriver=devicemapper version=1.12.6 Feb 01 20:13:57 hostname dockerd[24575]: time="2017-02-01T20:13:57.310491931+01:00" level=info msg="API listen on /var/run/docker.sock" Feb 01 20:13:57 hostname docker_service_helper.sh[24576]: Docker is alive Feb 01 20:13:57 hostname systemd[1]: Started Docker Application Container Engine. Feb 01 20:14:34 hostname dockerd[24575]: time="2017-02-01T20:14:34.042534237+01:00" level=error msg="Handler for POST /v1.24/containers/typo3-db/start returned error: Unknown runtime specified oci" Feb 01 20:14:34 hostname dockerd[24575]: time="2017-02-01T20:14:34.045480384+01:00" level=error msg="Handler for POST /v1.24/containers/typo3-web/start returned error: Unknown runtime specified oci"