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

wicked.box startup race condition ("Timeout") #202

Closed
DonMartin76 opened this issue Jun 3, 2019 · 0 comments
Closed

wicked.box startup race condition ("Timeout") #202

DonMartin76 opened this issue Jun 3, 2019 · 0 comments
Milestone

Comments

@DonMartin76
Copy link
Member

If the Postgres container is not yet 100% ready when wicked.box is started up, it can happen that wicked.box exits before it has actually been able to initialize itself.

This is particularly naughty, as AutoRemove is specified and set to true. This means you never even saw the logs.

Workaround:

  • Make sure Postgres is really running before you start wicked in a box

Possible Fix:

  • Use RestartPolicy: unless-stopped and manually remove the container when stopping instead of using AutoRemove: true.
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