Matias Calderini
10/19/2024, 5:29 PMprefect.utilities.dockerutils.BuildError: manifest for prefecthq/prefect:3.0.11-python3.11 not found: manifest unknown: manifest unknown
The deploy call looks like this:
my_function.deploy(
name=deployment_name,
work_pool_name="my-docker-pool",
image="my-first-deployment-image:tutorial",
push=False,
job_variables={
"image_pull_policy": "Never",
"auto_remove": True,
"env": {
"PREFECT_API_URL": "<http://host.docker.internal:4200/api>",
"PREFECT_SERVER_API_HOST": "0.0.0.0",
},
},
)
I can provide further information as required, but I am unsure where to start looking. This was working well with prefect 2. Notice that it is not my custom image that it does not found, but an underlying prefect oneRobin
10/19/2024, 9:09 PMMatias Calderini
10/19/2024, 9:15 PMNate
10/20/2024, 5:04 PMNate
10/20/2024, 5:04 PMmanifest unknownthis means "I can't find that image" which makes sense
Nate
10/20/2024, 5:06 PMMatias Calderini
10/20/2024, 5:06 PMNate
10/20/2024, 5:07 PMmy-first-deployment-image:tutorial
?Matias Calderini
10/20/2024, 5:17 PMFROM python:3.11 as base
FROM base as docker
RUN apt-get update && \
apt-get install -qy curl && \
curl -sSL <https://get.docker.com/> | sh
FROM docker as app
WORKDIR /app
RUN pip install httpx prefect-client prefect-docker
COPY ./src .
(essentially a docker-outside-docker setup)
But dockerfile for my-first-deployment-image:tutorial
is simpler:
FROM python:3.11 as base
RUN pip install prefect
WORKDIR /extraction
COPY ./* .
(which I assume could have used an install of prefect-client only)
These work without problem when setting build to false and building the image myself, so there might be something thereNate
10/20/2024, 5:20 PMMatias Calderini
10/20/2024, 5:24 PM