-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Build with --link
no longer works on Ubuntu 22.04 build 2.317.0
#10106
Comments
@chrisjohnson00 Thank you for bringing this issue to us, we are investigating on this issue and we will update you on this issue after our findings. |
Hi @chrisjohnson00, We tried with your repro steps it was succeeded with no errors. Kindly retry the same.
|
@RaviAkshintala I concur.
|
Could you please retry with the below modified Dockerfile.
|
yup, works. |
@chrisjohnson00 As suggested to use ./ or /src at the end of COPY instruction, it worked for me. Can you update me if it works for you or not. |
Yup, works Odd that it stopped working the original way |
Hi @chrisjohnson00 , We will be closing the issue, as workaround provided has worked. Thank you. |
Description
When building a Docker Container which contains a
COPY --link x y
command, commands which reference this path fail statingI have builds which succeed with the use of
--link
using the same version of the runner. However, all new builds fail consistently now. If it isn't the runner itself, then it could be the underlying disk infrastructure.FWIW - All our actions are pinned to tags via hashes, so there has been no change to the action code we run.
Platforms affected
Runner images affected
Image version and build link
Fails on
Last passing build was
Is it regression?
No?
Expected behavior
Successful container build
Actual behavior
Any Dockerfile reference to the path containing a link fails with the following error
Repro steps
A simple way to reproduce this is to build:
It will fail with the above error message.
Removing
--link
from theCOPY
results in a successful build.The text was updated successfully, but these errors were encountered: