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
When creating the build context the owner of the file should be changed, to whatever it needs to be. There are several issues that may arise here:
We do not know what the user wil be (except if --run-as-user is set), in case the K8S has custom POD security policies. How does k8s decide volume permissions??
If the volume is te be mounted into two containers c1 and c2 running with uids uid1 and uid2, respectively, what owner should we set? How does docker handle this?
The text was updated successfully, but these errors were encountered:
When creating the build context the owner of the file should be changed, to whatever it needs to be. There are several issues that may arise here:
--run-as-user
is set), in case the K8S has custom POD security policies. How does k8s decide volume permissions??The text was updated successfully, but these errors were encountered: