question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error running docker compose

See original GitHub issue
ERROR: 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:open
  • Created 2 years ago
  • Reactions:3
  • Comments:8

github_iconTop GitHub Comments

43reactions
scipionicommented, Sep 17, 2021

same issue but I changed

image: mher/flower

to

image: mher/flower:0.9.7

in docker-compose.yml

4reactions
eddebccommented, Feb 6, 2022

To add onto okamop’s answer;
According to Flower’s Docker page

Important Please note that from version 1.0.1 Flower uses Celery 5 and has to be invoked in the same style as celery commands do.

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 be specified after the flower sub-command.

This is the template to follow::

celery [celery args] flower [flower args]

With the fix in this commit

- ENTRYPOINT ["flower"]
+ CMD ["celery flower"] 

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.

  flower:
    image: mher/flower
    networks:
      - ${TRAEFIK_PUBLIC_NETWORK?Variable not set}
      - default
    env_file:
      - .env
    environment:
      - CELERY_BROKER_URL=amqp://guest@queue:5672//
    deploy:
      labels:
        - traefik.enable=true
        - traefik.docker.network=${TRAEFIK_PUBLIC_NETWORK?Variable not set}
        - traefik.constraint-label=${TRAEFIK_PUBLIC_TAG?Variable not set}
        - traefik.http.routers.${STACK_NAME?Variable not set}-flower-http.rule=Host(`flower.${DOMAIN?Variable not set}`)
        - traefik.http.routers.${STACK_NAME?Variable not set}-flower-http.entrypoints=http
        - traefik.http.routers.${STACK_NAME?Variable not set}-flower-http.middlewares=${STACK_NAME?Variable not set}-https-redirect
        - traefik.http.routers.${STACK_NAME?Variable not set}-flower-https.rule=Host(`flower.${DOMAIN?Variable not set}`)
        - traefik.http.routers.${STACK_NAME?Variable not set}-flower-https.entrypoints=https
        - traefik.http.routers.${STACK_NAME?Variable not set}-flower-https.tls=true
        - traefik.http.routers.${STACK_NAME?Variable not set}-flower-https.tls.certresolver=le
        - traefik.http.services.${STACK_NAME?Variable not set}-flower.loadbalancer.server.port=5555

I don’t know about the “Broker tab” comment and dropped it.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found