-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
ability to set file mode (when copying from Windows host to *nix container) #446
Comments
glebsts
changed the title
ability to set file mode when copying from Windows host to *nix container
ability to set file mode (when copying from Windows host to *nix container)
Aug 21, 2017
#467 please review |
actually found it to be useful in unix as well - I don't need to care which permissions file has in my host filesystem, in order to have specific permissions in container. |
rnorth
pushed a commit
that referenced
this issue
Nov 11, 2017
Merged
rnorth
pushed a commit
that referenced
this issue
Nov 11, 2017
rnorth
pushed a commit
that referenced
this issue
Nov 19, 2017
rnorth
pushed a commit
that referenced
this issue
Nov 19, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
MountableFile.getUnixFileMode()
asks for'unix:mode'
, and in case of non-posix system falls back to default0100644
, and sets that as file mode inside tar archive. If I want file to be writeable inside container (i.e. by logger in my jetty app), I need to do some additional trick withchmod
.I would like instead to set file mode with
copy()
command, i.e.builder.copy("entryname", "path_in_container", 777)
The text was updated successfully, but these errors were encountered: