-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
COPY --chown fails image build with unknown user #1603
Comments
We have the same issue. The problem is in the USER 1001 used inside Dockefile generated by Quarkus site. I asked a Red Hat engineering and she said is ok because:
Is this a bug or a wanted behaviour ? |
Just in case someone else stumbles upon this and wants a workaround: The package that contains But I'd rather want kaniko to just function the same way docker does - simply accepting that the user id does not exist and carry on... |
Actual behavior
Building a Docker image containing a COPY directive using
--chown
fails the build withI've created a repository as a minimal, complete and verifiable example which reproduces the problem I've noticed on GitLab CI, here
https://github.com/chris-asl/quarkus-dummy-project
It seems to be related with #477 and #1456, which are both closed due to no reproducibility.
@tejal29 In the provided MCVE, I can reproduce the error that's happening both on GitLab CI and my local workstation.
Please let me know if you need more information.
Expected behavior
The build of the image should succeed, copying the files inside the container layer, with the appropriate user id.
To Reproduce
Steps to reproduce the behavior:
./mvnw clean package
Additional Information
https://github.com/chris-asl/quarkus-dummy-project/blob/master/src/main/docker/Dockerfile.jvm
Can be seen from the provided dummy project: https://github.com/chris-asl/quarkus-dummy-project
gcr.io/kaniko-project/executor:v1.5.1-debug
with the repo digest beinggcr.io/kaniko-project/executor@sha256:e00dfdd4a44097867c8ef671e5a7f3e31d94bd09406dbdfba8a13a63fc6b8060
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: