-
Notifications
You must be signed in to change notification settings - Fork 51
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
feat: add an easy way to configure users and groups and /tmp #129
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job!
I'm wondering if we should create a kind of namespace for this kind of helpers.
Instead of nix2container.shadowLayer
, I would suggest nix2container.layers.shadow
.
Because, once we have nix2container.layers.shadow
, i'm pretty sure we would like nix2container.layers.tmp
to create /tmp
.
What do you think?
Otherwise, this lgtm!
Just like nixpkgs provides `dockerTools.shadowSetup`, nix2container needs a quick way to configure users, groups and permissions within the container. Here it is. @moduon MT-1075
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your comments, all attended.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your comments, all attended.
Would you please let workflows run? |
Tests are failing, but I think it's because of a lower-level issue that changes permissions when some derivation is in |
Just like nixpkgs provides
dockerTools.shadowSetup
, nix2container needs a quick way to configure users, groups and permissions within the container.Here it is.
@moduon MT-1075