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
For filesystem custom volumes, we currently have root:root as the initial owner of the volume.
This makes sense for system containers and VMs and is generally the correct behavior there.
But for OCI containers where the application may be running as non-root and where there isn't an init system to put the storage in place and correct ownership, having the ability to create a volume with a pre-defined owner would be quite useful.
This would likely look like 3 additional volume keys:
initial.uid
initial.gid
initial.mode
The text was updated successfully, but these errors were encountered:
For filesystem custom volumes, we currently have root:root as the initial owner of the volume.
This makes sense for system containers and VMs and is generally the correct behavior there.
But for OCI containers where the application may be running as non-root and where there isn't an init system to put the storage in place and correct ownership, having the ability to create a volume with a pre-defined owner would be quite useful.
This would likely look like 3 additional volume keys:
The text was updated successfully, but these errors were encountered: