Flower is not starting
See original GitHub issueGood day.
Couple days ago Flower stopped working and giving me next error, when trying to start the container.
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
I cross-checked all configs and they seem to be identical to ones in template itself.
All the other containers start and work just fine
EDIT: not working on macOS 11.4 with Docker Engine v20.10.7 as well as Ubuntu 20.04.2 LTS
Issue Analytics
- State:
- Created 2 years ago
- Comments:9
Top Results From Across the Web
Celery works, but with flower doesn't work - Stack Overflow
Flower does not process tasks. You must run both, then Flower can be used as a monitoring tool. Run celery: celery -A tasks...
Read more >Installation — Flower 1.0.1 documentation
The key takeaway here is that the Celery app's arguments have to be specified after the celery command and Flower's arguments have to...
Read more >Setting Up Celery, Flower, & RabbitMQ for Airflow - Medium
But before we start using Celery Executor, we must set up Celery, Flower ... Start the server to check if it is running...
Read more >flower - PyPI
Features · Task progress and history · Ability to show task details (arguments, start time, runtime, and more) · Graphs and statistics.
Read more >Flower — Airflow Documentation
Basic authentication for Celery Flower is supported. You can specify the details either as an optional argument in the Flower process launching command,...
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
@kgorshkoff The problem is that
mher/flower
in the docker compose file points to latest, and latest is no longer compatible with the docker compose file. If you override the image and point tomher/flower:0.9.7
then everything works fine.I’ll submit a PR to at least get things installing again
This stack has saved me so much time in other ways I can forgive a little time wasted on a fixable issue in the repo. Maybe its time to fork or see if tiangolo wants to turn over PR control to someone with more time. It does feel tragic knowing an unpatched repo is being cloned hundreds of times with a bug that is going to cost thousands of hours of time, all while the fix is sitting in a PR queue. I guess it’s a lesson to check the issues tab before diving into a day long debug adventure. I should have done it the other way around.