Closed robdejonge closed 3 months ago
same here.
Yeah, image was missing up
file after I changed it to run as oneshot
. I added that in. It should work now.
I also observed that you have container paths as /app/...
. This has changed in recent release to /config/...
. Please go through README carefully and make necessary changes.
Thanks for the fix!
Describe the bug Container does not seem to be starting.
To Reproduce My docker-compose.yaml :
My config.yaml :
After removing existing image and container and thus downloading the latest version, output when I run 'docker compose up' after download looks like this :
The container remains up, with the following further information from within :
I've let it run for 20 minutes and nothing ever happens.
I'm not sure if I'm doing something wrong in my host config, or if this a recently introduced issue to the image. Apologies if it's the former.