celeryworker.dockerfile exiting with code: 1 about full-stack-fastapi-mongodb HOT 7 CLOSED

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"
RUN pipx install "hatch==$HATCH_VERSION"
RUN hatch env prune && hatch env create production
RUN chmod +x /app/worker-start.sh

from full-stack-fastapi-mongodb.

Hey @aidancahill, thanks for your patience on this issue.

To start, could you share if you have the file /app/worker-start.sh in your backend directory? In your generated app the pathname should look like this {project_name}/backend/app/worker-start.sh? If not that may be the root issue. It may have been accidentally deleted or removed. Let me know if that helps. If not, we can follow up with this in a formal JIRA ticket.

from full-stack-fastapi-mongodb.

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
set -e

hatch run python /app/app/celeryworker_pre_start.py
hatch run celery -A app.worker worker -l info -Q main-queue -c 1

from full-stack-fastapi-mongodb.

I have the same issue.

from full-stack-fastapi-mongodb.

I am also getting this issue.

from full-stack-fastapi-mongodb.

Thanks @csouflis! I opened https://jira.mongodb.org/browse/PYTHON-4351 to track this bug.

from full-stack-fastapi-mongodb.

I applied the change in #38.

from full-stack-fastapi-mongodb.