Bug 1267320
Summary: | Cloud-init (re)start Docker Daemon | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Eric Jones <erjones> |
Component: | cloud-init | Assignee: | Lars Kellogg-Stedman <lars> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.1 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-30 13:32:25 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: |
Description
Eric Jones
2015-09-29 15:49:24 UTC
Try running: systemctl --no-block restart docker The problem is that docker can't start until cloud-init has finished running, so you've got yourself deadlocked. That worked. Thank you. Is there any documentation on that? > Is there any documentation on that? Well, there's the systemd documentation, describes the --no-block option: http://www.freedesktop.org/software/systemd/man/systemctl.html It looks like there is a blog post out there on this particular issue: http://dustymabe.com/2015/08/03/installingstarting-systemd-services-using-cloud-init/ Okay, I appreciate it. |