Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker-compose up -d issue | OCI runtime create failed #520

Closed
syrniellow opened this issue Jun 7, 2023 · 6 comments
Closed

docker-compose up -d issue | OCI runtime create failed #520

syrniellow opened this issue Jun 7, 2023 · 6 comments
Labels

Comments

@syrniellow
Copy link

syrniellow commented Jun 7, 2023

Hi, I get the following issue in the last stage before starting the container (<project-name>:flower-1).

# command
docker-compose up -d

Assuming the project name is "myapp"

 ✔ Network myapp_default                                                                                                                                  C...                         0.0s 
 ✔ Network myapp_traefik-public                                                                                                                           Created                      0.0s 
 ✔ Volume "myapp_app-db-data"                                                                                                                             Created                      0.0s 
 ✔ Container myapp-db-1                                                                                                                                   St...                        0.4s 
 ⠿ Container myapp-flower-1                                                                                                                               Starting                     1.3s 
 ✔ Container myapp-queue-1                                                                                                                                Started                      0.7s 
 ✔ Container myapp-frontend-1                                                                                                                             Started                      0.7s 
 ✔ Container myapp-proxy-1                                                                                                                                Started                      1.1s 
 ✔ Container myapp-backend-1                                                                                                                              Started                      1.1s 
 ✔ Container myapp-pgadmin-1                                                                                                                              Started                      1.2s 
 ✔ Container myapp-celeryworker-1

 ! backend The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested                              0.0s 
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "--broker=amqp://guest@queue:5672//": stat --broker=amqp://guest@queue:5672//: no such file or directory: unknown
@syrniellow syrniellow changed the title OCI runtime create failed docker-compose up -d issue | OCI runtime create failed Jun 7, 2023
@FunkyDialUpDude
Copy link

Same issue here.

@Tom-Camp
Copy link

Tom-Camp commented Jun 19, 2023

I was able to "solve" this by downgrading the version of Flower to 0.9.5

flower:
-  image: mher/flower
+  image: mher/flower:0.9.5

@Tom-Camp
Copy link

Tom-Camp commented Jun 19, 2023

Ah, but it seems a better solution is to add the CELERY_BROKER_URL as an environment variable:

    deploy:
        ...
-    command:
-      - "--broker=amqp://guest@queue:5672//"
-      # For the "Broker" tab to work in the flower UI, uncomment the following command argument,
-      # and change the queue service's image as well
-      # - "--broker_api=http://guest:guest@queue:15672/api//"
+    environment:
+       - CELERY_BROKER_URL=amqp://guest@queue:5672//

#420 (comment)

@dudil
Copy link
Contributor

dudil commented Mar 13, 2024

@syrniellow - if this is an issue on Mac M model, there is a workaround I've mentioned in #707
I hope you will find that useful.

@tiangolo
Copy link
Member

Yep, I think the issue would be what @dudil mentioned.

Have in mind that the latest version doesn't use Celery and Flower. But in any case, if you have similar issues, the can probably be handled with the same trick. 🤓

Copy link

Assuming the original issue was solved, it will be automatically closed now. But feel free to add more comments or create new issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants