error in prefect when i specify my new image in the
pull
step of the prefect.yaml. after researching that error, i'm seeing it may be due to memory size issues and am wondering about the limits on pods spun up by prefect - this image's size is 492.5 MB - however, our other images are close to that size and have no issues. could that be the issue, or do you have any other recommendations on how to fix?
k
Kevin Grismore
03/21/2024, 6:24 PM
are you able to share the dockerfile? sounds more like the pod has problems either pulling the image or starting up
i
isabel obregon
03/21/2024, 6:45 PM
yeah sure- this is the dockerfile
Copy code
FROM .../prefect/prefect-alpine
# Set the working directory in the container
WORKDIR /opt/prefect/debugging-service
# Copy all necessary contents
COPY . /opt/prefect/debugging-service
COPY ./debugging ./debugging
# Install Poetry
RUN pip install poetry
# Disable creation of .venv (use system python env instead)
RUN poetry config virtualenvs.create false
# Set the working directory to debugging for poetry install
WORKDIR /opt/prefect/debugging-service/debugging
# Install project dependencies
RUN poetry install --no-interaction --no-ansi
its a bit wonky bc we are trying to create an image based on a subservice (./debugging), but need to copy the entire service (i called it debugging-service above) bc the poetry dependencies rely on the outer service
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.