-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[fusefs]: docker in workspace not working #6992
Comments
/schedule |
@csweichel: Issue scheduled in the workspace team (WIP: 0) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@mrsimonemms Thanks, verified to be working on gke-guide based deployments: After adding
|
maybe related to #7793 |
I've recently switched the default config method to |
Bug description
It seems that running
docker run -it --rm <container>
is returning the dreadedproc
error again when deployed with the Installer. Thanks to @csweichel's suggestion, it seems to be to work with thefsShiftMethod
- if you set tofuse
(the default) then it fails. Setting toshiftfs
makes it workThis is NOT an issue in the SaaS offering.
Steps to reproduce
Run
docker run -it --rm node
on a GKE or Azure cluster. Must haveworkspace.runtime.fsShiftMethod
set tofuse
- setting toshiftfs
seems to workWorkspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
ws-daemon logs (redacted)
Azure
GCP
To my observation, these seem to be the same basic problem between Azure and GCP
The text was updated successfully, but these errors were encountered: