Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assist with fleet/docker dependency issues #2

Open
lfittl opened this issue Apr 19, 2015 · 0 comments
Open

Assist with fleet/docker dependency issues #2

lfittl opened this issue Apr 19, 2015 · 0 comments

Comments

@lfittl
Copy link
Owner

lfittl commented Apr 19, 2015

moby/moby#7228 (comment)
moby/moby#6791 (comment)
https://groups.google.com/forum/#!msg/coreos-dev/qbVrYpDUtG8/t88RbGD_assJ
https://coreos.com/docs/launching-containers/launching/getting-started-with-systemd/

The issue is that systemd state does not reflect docker state (i.e. container isn't actually ensured to be running), and additionally does not ensure that the service is actually available.

e.g. the database needs sometime to start up until it can actually accept connections.

systemd should allow mark that dependency as fulfilled once the service is actually available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant