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
Hi Bruce
thanks a lot for the amazing work!
i just tested the docker container and i would like to know if there is a way to mount the current credentials without changing their ownership within the container. just to better explain
imagine i run as root and i have my credentials there, if i run the container as suggested
With griduser I was primarily concerned with not running clients as root in the container. Not that it's a problem for the container, but some of the clients would complain.
The case you specify will indeed fail - I guess I should create a test case for that (thanks!)
I will check the docker documentation, but I think the only way to win that game is to run the container as root.
Hi Bruce
thanks a lot for the amazing work!
i just tested the docker container and i would like to know if there is a way to mount the current credentials without changing their ownership within the container. just to better explain
imagine i run as root and i have my credentials there, if i run the container as suggested
docker run -u griduser -ti --rm --name ui -v $HOME/.globus:/home/griduser/.globus quay.io/egi/ui /bin/bash
the credentials available under the griduser home will be owned by root
is there a way in docker to mount a volume and give the ownership to the user specified via -u?
thanks
Andrea
The text was updated successfully, but these errors were encountered: