starting with 'docker-compose up' fails
See original GitHub issueHi! Starting with ‘docker-compose up’ doesn’t seem to work for me.
I see a kuzzle_kuzzle_1 exited with code 0
green entry in the startup logs.
The main branch works fine.
Any idea what can be wrong?
Thanks.
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
docker-compose up fails when docker-compose run is ...
the problem here that docker-compose up does not wait untill the db is running. you may use wait-for-it.sh , see this. example :...
Read more >docker compose up - Docker Documentation
When the command exits, all containers are stopped. Running docker compose up --detach starts the containers in the background and leaves them running....
Read more >`docker compose up` doesn't start containers (error message
docker compose up doesn't start containers (error message: "volume [volume name] already exists but was not created by Docker Compose.
Read more >Docker compose up build fails to update container
The Problem · up start the service your_service · --build build the image if it does not exist or has changed. Use cache...
Read more >How to get detailed error message using docker-compose up ...
means that Docker tried to run the dotnet executable inside the container, but it couldn't start because the dotnet binary in the image...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Should be better now.
Try:
I close this issue, let us know if you still have a problem. Thanks for your contribution!
OK I have an intuition of what is wrong… We’ll see tomorrow what to do with the team.
Right now you can safely use the debug.yml file or create your own based on it (to not start the Rabbit server for instance, if you do not need MQ protocols). We’ll let you know about the resolution of this problem.
Thank you very much for taking time to report this! We all appreciate it 😃