You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have set a new umask value to my containers.conf (0017) and now my containerized application writes it's log files with the permissions I want it to write them. BUT! As I was setting it up and tried to test the propagation of the settings by entering the running container with 'podman exec' the umask value was the default one (0022) instead of what was visible in the containers.conf and podman inspect container.
So the question follows. Why the umask setting is different in these cases?
The text was updated successfully, but these errors were encountered:
Discussed in #19712
Originally posted by Joniteus August 23, 2023
Hi,
I have set a new umask value to my containers.conf (0017) and now my containerized application writes it's log files with the permissions I want it to write them. BUT! As I was setting it up and tried to test the propagation of the settings by entering the running container with 'podman exec' the umask value was the default one (0022) instead of what was visible in the containers.conf and podman inspect container.
So the question follows. Why the umask setting is different in these cases?
The text was updated successfully, but these errors were encountered: