Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion about PVC usage for non root containers in OpenShift default namespace #4053

Closed
maysunfaisal opened this issue Sep 28, 2020 · 1 comment · Fixed by #4092
Closed
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

Comments

@maysunfaisal
Copy link
Contributor

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, then odo 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.

@maysunfaisal maysunfaisal added area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. area/storage area/openshift Issues or PRs related to OpenShift labels Sep 28, 2020
@maysunfaisal
Copy link
Contributor Author

We want odo to spit out a warning saying we're running in default namespace and things may not run as expected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant