-
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
Starting docker containers failing with "mount through procfd: operation not permitted" #5171
Comments
I also see this issue, and someone else pointed it out on our community page. |
The workspace contains |
Resolved and in production. |
@ghuntley is the resolution rolled out incremental? I'm still encountering this issue on "ws-eu15". On "ws-eu16" it works. (Repo for reproduction: https://github.com/ChristianHuff-DEV/gitpod-4573) |
Indeed. We have problem with 15, but cant recreate our repo in 16 - all times it creates on 15. |
Not resolved. Every time eu15, and every time error. |
/schedule |
@csweichel: Cannot schedule issue - issue does not belong to a team. Use /team to specify one. 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. |
/team workspace |
/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. |
/assign |
Bug description
When starting a container through the terminal, it fails with:
Steps to reproduce
Expected behavior
No response
Example repository
No response
Anything else?
Didn't find a duplicate, maybe related to #5090
This wasn't a problem few days ago. Also, another friend had this same error, maybe more people may face this.
The text was updated successfully, but these errors were encountered: