-
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
directory permissions change #846
Comments
Hi, thank you @ataillefer |
Don't know, can you please provide the new Dockerfile? |
We need to reproduce this bug to make sure this still exists. |
Is this related to #721? |
This bug still exists in v0.18.0 For example, this: https://github.com/ForgeRock/forgeops/tree/master/docker/7.0/ds/idrepo Results in The same image built with docker works fine (/opt/opendj remains owned by the forgerock user) If we add |
Just a quick check, does it behave the same without the final slash in the target directory?
instead of
|
Just retested without the
|
@ataillefer based on my debugging the issue is related to snapshots and not the builds. You can add a |
OK @maxres-fr good to know, we'll try to test soon the supposedly fixed |
similar issue, builds that work fine built w/ normal Docker, get weird permissions errors after being built by Kaniko. (tried 0.15.x + 0.18.0) |
Hello, We've got a similar issue with an image extending another one. We used kaniko v0.18.0. Here below the corresponding Dockerfile:
The output of
So the file is copied with the right permission. But as you can see with The output of
We clearly see that The output of
We can see that @maxres-fr what is the next step on this topic? |
@kevinleturc I'm not entirely sure here. Using It's great to see the issue reproduced. I've tried to debug a little of this, but my hunch is that it's related to the snapshots and not the COPY or at least not directly related command but I don't want to lead anyone down the wrong path. FWIW @wstrange and I work on the same code bases. |
Is it possible to merge #1257 ? I have the same permissions problems with the parent folder of my |
Hello, |
0.24 has something like this still. My |
in 0.24.0 I also see:
In the resulting image:
edit: This is with |
I am still encountering this behavior in 0.22.0 (#1166 was first released in 0.20.0). Specifically, I'm seeing directories becoming owned by root after files under the directory are added. Additionally, as @bitsofinfo mentioned, chowning the directory does not fix ownership of the directory. Adding --single-snapshot does avoid the problem. |
Actual behavior
A clear and concise description of what the bug is.
Expected behavior
A clear and concise description of what you expected to happen.
To Reproduce
Steps to reproduce the behavior:
app directory permissions app: app
Same dockerfile if i use docker build , the new images app and app/lib is not change ,This is what we need。
Additional Information
docker run --env DOCKER_CONFIG=/kaniko -v /tmp/app:/workspace -v /root/.docker/config.json:/kaniko/config.json gcr.io/kaniko-project/executor:latest -d reg.xx.com/mid/test
gcr.io/kaniko-project/executor:latest
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: