Cannot get the Dockerfile COPY command to work (OD-2029)

Glenn D. opened 1 year ago

Hey everyone,

I am trying to build a docker image using the Docker Image > Build Image step. However, it keeps failing on the COPY step:

#7 [3/4] COPY CC/bin/Release/net8.0/linux-x64/publish/* /CC/
#7 ERROR: lstat /tmp/buildkit-mount2575296789/CC/bin/Release/net8.0/linux-x64/publish: no such file or directory

I have tried leaving the "Build Path" setting of the Build Image step empty and tried ".". I have tried various paths as the source of the COPY command, but every time I get the same error.

I added an "ls" command to see what was available. The source path I use in my COPY command exists, the one shown as the "lstat" path does not. I also have no clue where the "/tmp/buildkit-mount2575296789" part of the path is coming from.

Clearly I'm not understanding how to access the built files from the workspace in order to copy them to the image.

Does anyone have an idea of what I could be doing wrong?

Greetings, G.

Activities

Robin Shen commented 1 year ago

If build path is left empty or set as ".", source directory of COPY command will be relative to job workspace. Please make sure that the directory "CC/bin/Release/net8.0/linux-x64/publish" exists in the job workspace before running the build image step. If it does not work as expected, please create an example project on this site to demonstrate the issue.
Glenn D. commented 1 year ago
@robin In the log file I can see the path when calling LS:

/onedev-build/workspace/CC/bin/Release/net8.0/linux-x64/publish

So the path seems to be there. Oddly enough in the error message it shows me the path:

lstat /tmp/buildkit-mount2575296789/CC/bin/Release/net8.0/linux-x64/publish: no such file or directory

I'm not sure where the part "/tmp/buildkit-mount2575296789/" comes from.

Could it be a configuration issue for the runner/executor?

I will try to create an example project to upload here.
Robin Shen commented 1 year ago

I'm not sure where the part "/tmp/buildkit-mount2575296789/" comes from.

Maybe some magic path used by docker container drive. It also reports path like this if the source path I specified to copy can not be found in job workspace.
Robin Shen changed state to 'Closed' 1 year ago
Previous Value Current Value
Open

Closed
Robin Shen commented 1 year ago

Reopen if there is more info.
jbauer commented 1 year ago

Do you have a .dockerignore in the project?
Login to comment

Previous Value	Current Value
Open	Closed

Type	Question
Priority	Normal
Assignee	Cody Robinson
Labels	No labels

Issue Votes (0)

Watchers (3)

Reference

OD-2029