-
Notifications
You must be signed in to change notification settings - Fork 429
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
panic: user: unknown userid
in a non-root container without user mapping
#877
Comments
panic: user: unknown userid
in a rootless container without user mappingpanic: user: unknown userid
in a non-root container without user mapping
Thanks @czka, We will discuss this issue with the team, and fix them accordingly. Closing this issue for now, since you have workaround for this. |
@raj-prince IMO the ticket should stay open until the underlying issue is fixed. |
I run into the same issue, as I am testing the GCS Fuse CSI Driver. One customer is asking us to run the gcsfuse in a sidecar that uses a non-root uid/gid. I tested an arbitrary uid/gid 1000, but got the same error from gcsfuse I believe the error comes from the code According to the discussion golang/go#38599, the golang os/user package cannot load an arbitrary uid/gid if the uid/gid does not exist in My solution is to do
Then I chose That being said, I still think it's worth it to fix the uid/gid check logic in gcsfuse because this issue prevents users from running gcsfuse binary in a container with an arbitrary uid/gid. |
As mentioned in #877 (comment) , we will evaluate this request and update here accordingly. Till then, we suggest to use the workaround mentioned in #877 (comment). |
this workaround helped me. without |
gcsfuse (at least the latest 0.41.10 that I tried) panics in a non-root container without a user mapping.
An example with Bitnami Wordpress image:
docker pull bitnami/wordpress
docker inspect bitnami/wordpress:latest | grep -i user
:Adapt this Google's example to try Wordpress on Cloud Run with gcsfuse (not providing details here - irrelevant).
Deploy to Cloud Run and observe the error for command
gcsfuse --debug_gcs --debug_fuse --foreground $BUCKET /mnt/gcs
:Edit: FYI, the issue is gone after giving the user
1001
a name in my Dockerfile derived from the Bitnami Wordpress image, as follows:That's only a workaround though.
The text was updated successfully, but these errors were encountered: