Joseph Haaga

11/12/2020, 4:02 PM
I’m working on a Python utility to automate the registration/deployment of Flows for our Prefect users; I noticed that the Dockerfile generated by
contains a COPY statement to add
to the image, but uses an absolute path (which
docker build
treats as a relative path from the build context)
Copy code
COPY /absolute/path/on/my/machine/ /opt/prefect/
This causes the following error:
Copy code
Step 6/16 : COPY /absolute/path/on/my/machine/ /opt/prefect/
COPY failed: stat /var/lib/docker/tmp/docker-builder852791584/absolute/path/on/my/machine/ no such file or directory
However, this works fine when I manually update the Dockerfile to use a relative path to
Would this constitute an issue? Or am I circumventing an intentional design decision?


11/12/2020, 6:10 PM
Hi @Joseph Haaga! I’m not sure if this is intentional or an issue. If you’re unsure, I might suggest opening a github discussion and then you can transition to an issue if necessary