-
Notifications
You must be signed in to change notification settings - Fork 95
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
celeryworker.dockerfile exiting with code: 1 #25
Comments
Hey @aidancahill, thanks for your patience on this issue. To start, could you share if you have the file |
Hey @Jibola, Thanks for taking the time, Yes in the directory {project_name}/backend/app/, I have a worker-start.sh. I was pretty sparse with the amount of context I provided in the original post, happy to provide any additional generated files to replicate the bug. (The content of worker-start.sh) #! /usr/bin/env bash hatch run python /app/app/celeryworker_pre_start.py |
I have the same issue. |
I am also getting this issue. |
Hey guys I solved the issue by separating out the RUN commands in the celeryworker.dockerfile, like this: RUN python -m pip install --no-cache-dir --upgrade pip "pipx==$PIPX_VERSION" |
Thanks @csouflis! I opened https://jira.mongodb.org/browse/PYTHON-4351 to track this bug. |
I applied the change in #38. |
Docker compose build command exits with code: 1, line 17 - 20 in the celeryworker.dockerfile in the backend directory. Getting this response in the terminal "23.63 Environment
production
is not defined by project config23.65 chmod: cannot access '/app/worker-start.sh'$'\r': No such file or directory
failed to solve: process "/bin/sh -c python -m pip install --no-cache-dir --upgrade pip "pipx==$PIPX_VERSION"\r\npipx install "hatch==$HATCH_VERSION"\r\nhatch env prune && hatch env create production\r\nchmod +x /app/worker-start.sh\r\n" did not complete successfully: exit code: 1"
Am I doing something wrong here? I definitely can be making a dumb config mistake. Default configuration to localhost.
The text was updated successfully, but these errors were encountered: