Skip to content
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.

Sign up for GitHub

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

Jump to bottom

reproducible_builds: ensure that umask doesn't affect the container build #3

Open
praiskup opened this issue Apr 6, 2017 · 1 comment
Open

reproducible_builds: ensure that umask doesn't affect the container build #3

praiskup opened this issue Apr 6, 2017 · 1 comment
Labels
enhancement

Comments

@praiskup
Copy link
Contributor

praiskup commented Apr 6, 2017

  • git doesn't track file permissions, thus
  • git clone initiates the permissions according the user's umask value
  • docker build just copies the files as-is into container
  • especial problems are with root/usr directory created by ADD root / command, this affects the whole image (/usr directory might be unreadable)

In RPMs' specfiles, we explicitly set the permissions in %install phase (or by %attr in %files), though there's no such way in Dockerfile.
@praiskup praiskup changed the title Ensure that umask doesn't affect the container build reproducible_builds: ensure that umask doesn't affect the container build Apr 6, 2017
@omron93
Copy link
Contributor

omron93 commented Apr 6, 2017

Related to sclorg/mariadb-container#29

@praiskup praiskup mentioned this issue Nov 21, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@praiskup @omron93