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.
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
AutoRemoveis specified and set totrue. This means you never even saw the logs.Workaround:
Possible Fix:
RestartPolicy: unless-stoppedand manually remove the container when stopping instead of usingAutoRemove: true.