Error running docker compose
See original GitHub issueERROR: for akt_flower_1 Cannot start service flower: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "--broker=amqp://guest@queue:5672//": stat --broker=amqp://guest@queue:5672//: no such file or directory: unknown
ERROR: for proxy Cannot start service proxy: driver failed programming external connectivity on endpoint akt_proxy_1 (9f435975e1e50df3035943f827308355da1df9d8c9d015c80906aa88c2a846dd): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use
ERROR: for flower Cannot start service flower: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "--broker=amqp://guest@queue:5672//": stat --broker=amqp://guest@queue:5672//: no such file or directory: unknown
ERROR: Encountered errors while bringing up the project.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:8
Top Results From Across the Web
Getting error on running docker-compose up - Stack Overflow
I am trying to run my python code through docker-compose. It is not a flask app so I didn't provide a port number...
Read more >How to get detailed error message using docker-compose up ...
The error is occurring during the build process. You should see the same results when you run docker-compose build . This error:
Read more >Docker-compose up throwing error | Edureka Community
ERROR: Version in "./docker-compose. yaml" is unsupported. You might be seeing this error because you're using the wrong Compose file version.
Read more >Docker compose run --entrypoint error: usr/local/bin/npm
Description I'm basically getting an npm error on compose v2 but works on compose v1. I recently updated from v1 in order to...
Read more >Python error occurs when running docker-compose in ubuntu ...
so I run the yaml (yml) file on the windows docker desktop without any problem, but when I tried setting up my containers...
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
same issue but I changed
to
in docker-compose.yml
To add onto okamop’s answer;
According to Flower’s Docker page
With the fix in this commit
Which means we also need to delete the
command:
block for Flower to start correctly.I ran into a Flower 0.9.7 issue that is resolved in their latest container image and couldn’t continue using version 0.9.7.