Uh oh!
There was an error while loading. Please reload this page.
Add missing interface to set init processes Umask - #706
Conversation
rhatdan
commented
Jul 13, 2020
@mrunalp PTAL |
rhatdan
commented
Jul 13, 2020
rhatdan
commented
Jul 13, 2020
@haircommander PTAL |
zhouhao3
commented
Jul 13, 2020
I think we need to add corresponding options in the generate function to call this function. |
eadda1f to
829dfc5Comparerhatdan
commented
Jul 13, 2020
@q384566678 Added. |
haircommander
commented
Jul 13, 2020
LGTM, thanks @rhatdan |
LGTM |
Umask is a field specified in the runtime spec, but we don't have a method to set it in runtime-tools. Some users might want to modify the default Umask of a container. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
commented
Jul 14, 2020
philips
commented
Jul 14, 2020
I am no longer a maintainer FYI 👍 |
rhatdan
commented
Jul 14, 2020
@philips Your name is still listed, sorry for bothering you. |
LGTM |
philips
commented
Jul 14, 2020
@rhatdan where is it listed? I think i am gone from maintainers. |
cyphar
commented
Jul 15, 2020
Yeah the @opencontainers/runtime-tools-maintainers list needs to be updated. /cc @caniszczyk? |
| func (g *Generator) SetProcessUmask(umask uint32) { | ||
| g.initConfigProcess() | ||
| g.Config.Process.User.Umask = umask | ||
| } |
There was a problem hiding this comment.
This has changed to be an *uint32 with opencontainers/runtime-spec@d3f079a, which breaks compatibility between the tools and the spec of both latest master branches.
There was a problem hiding this comment.
Just found the same thing :)
There was a problem hiding this comment.
So, there is a PR to fix it (#708) but apparently it requires a new release of runtime-specs, for which there is an issue opened (opencontainers/runtime-spec#1052) but it's not yet done so...
Umask is a field specified in the runtime spec, but we don't
have a method to set it in runtime-tools. Some users might
want to modify the default Umask of a container.
Signed-off-by: Daniel J Walsh dwalsh@redhat.com