Bug 1455749
| Summary: | Installer is hanging at Task "Start the Container Engine service" when using docker system container | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gan Huang <ghuang> |
| Component: | Containers | Assignee: | Jhon Honce <jhonce> |
| Status: | CLOSED ERRATA | QA Contact: | Gan Huang <ghuang> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.6.0 | CC: | aos-bugs, ghuang, gscrivan, jokerman, mmccomas, sdodson, smilner, smunilla |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-10 05:25:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1450307 | ||
|
Description
Gan Huang
2017-05-26 02:32:45 UTC
this may be caused by using systemd notifications in the Docker container. I've seen this issue when using an old version of runC, Atomic Host 7.3.4 already has an updated runC that supports sd-notify correctly.
I've tried also on Atomic Host 7.3.5 and it works fine for me.
What version of runc are you using? What does "systemctl status container-engine" show?
Here I have:
$ runc --version
runc version 1.0.0-rc3
commit: cafb8d8755dc2b990fc73fbf7bff62f534da9219-dirty
spec: 1.0.0-rc5
$ systemctl status container-engine
● container-engine.service - Docker service
Loaded: loaded (/etc/systemd/system/container-engine.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/container-engine.service.d
└─custom.conf
Active: active (running) since Mon 2017-05-29 10:44:38 UTC; 36min ago
Main PID: 743 (runc)
Memory: 109.5M
$ sudo atomic images list | grep container-engine
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7/container-engine latest a3ccc45997e0 2017-05-29 10:56 ostree
It works for runc 1.0.0-rc5 as well. However, I believe the versions before 7.3 not have a version of runc which is new enough to handle some of the feature updates. After talking with some folks it looks like this is a container issue that is being worked on. Moving the ownership over to jhonce so he can update as work progresses. An updated container build is ready for testing. container-engine service can be started successfully. atomic-1.17.2-4.git2760e30.el7.x86_64 # atomic --version 1.17.1 runc-1.0.0-6.gite800860.el7.x86_64 # runc --version runc version 1.0.0-rc3 commit: cafb8d8755dc2b990fc73fbf7bff62f534da9219-dirty spec: 1.0.0-rc5 # docker version Client: Version: 1.12.6 API version: 1.24 Package version: docker-1.12.6-28.git1398f24.el7.x86_64 Go version: go1.7.4 Git commit: 1398f24/1.12.6 Built: Wed May 17 01:16:44 2017 OS/Arch: linux/amd64 Server: Version: 1.12.6 API version: 1.24 Package version: docker-1.12.6-28.git1398f24.el7.x86_64 Go version: go1.7.4 Git commit: 1398f24/1.12.6 Built: Wed May 17 01:16:44 2017 OS/Arch: linux/amd64 # atomic images list |grep container- brew-xxxx.redhat.com:8888/rhel7/container-engine latest 0fd49accf210 2017-06-05 02:16 ostree Moving to verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1716 |