To deploy your application across the swarm, use `docker stack deploy`.
Creating network "klub_default" with the default driver
Creating klub_redis_1 ... done
Creating klub_postgres_1 ... done
Creating klub_web_1 ... done
Creating klub_celery_1 ... error
Creating klub_celery-beat_1 ...
Creating klub_flower_1 ... done
Creating klub_celery-beat_1 ... error
e or directory: unknown
ERROR: for klub_celery-beat_1 Cannot start service celery-beat: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/klub-v/venv/bin/celery": stat /klub-v/venv/bin/celery: no such file or directory: unknown
ERROR: for celery Cannot start service celery: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/klub-v/venv/bin/celery": stat /klub-v/venv/bin/celery: no such file or directory: unknown
ERROR: for celery-beat Cannot start service celery-beat: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/klub-v/venv/bin/celery": stat /klub-v/venv/bin/celery: no such file or directory: unknown
ERROR: Encountered errors while bringing up the project.
Expected behavior
Celery and celery beat Docker container should launch without error.
Describe the bug Celery and celery beat fail to lauch during docker-compose up.
To Reproduce Steps to reproduce the behavior:
docker-compose build --build-arg UID=$UID
docker-compose up
Expected behavior Celery and celery beat Docker container should launch without error.