Discussion about PVC usage for non root containers in OpenShift default namespace #4053
Labels
area/devfile-spec
Issues or PRs related to the Devfile specification and how odo handles and interprets it.
area/openshift
Issues or PRs related to OpenShift
When debugging issue #4027, we noticed that any stack user is going to face a permission issue if they modify the pvc volume mount path outside of what is prescribed by the image in default namespace.
For example, if the image gave write permissions to a path
/mypath1
and the devfile pvc uses it in default namespace, it is fine. However if the user updates their devfile pvc volume mount path to/mypath2
, thenodo push
is going to fail because/mypath2
does not have the write permission but/mypath1
did which was set by the image's dockerfile.This however, is not an issue in non-default OpenShift namespaces. The pvc path has the correct ownership for the arbitrary user id and is able to read/write in the pvc path.
The text was updated successfully, but these errors were encountered: