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

Starting docker containers failing with "mount through procfd: operation not permitted" #5171

Closed
adi-g15 opened this issue Aug 12, 2021 · 12 comments · Fixed by #5407
Closed
Assignees
Labels
groundwork: awaiting deployment priority: highest (user impact) Directly user impacting team: workspace Issue belongs to the Workspace team type: bug Something isn't working

Comments

@adi-g15
Copy link

adi-g15 commented Aug 12, 2021

Bug description

When starting a container through the terminal, it fails with:

docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "proc" to rootfs at "/proc" caused: mount through procfd: operation not permitted: unknown.

image

Steps to reproduce

  1. Open gitpod with any repo, eg. https://gitpod.io/#https://github.com/adi-g15/zeeve-learnings
  2. docker run -it ubuntu

I tried with multiple images, all failed with same error, including archlinux, custom images, hyperledger sawtooth

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.

@pawlean pawlean added the type: bug Something isn't working label Aug 12, 2021
@pawlean
Copy link
Contributor

pawlean commented Aug 12, 2021

I also see this issue, and someone else pointed it out on our community page.

@csweichel
Copy link
Contributor

The workspace contains runc in version 1.0.1 which breaks right now. We have a fix on main (#5139) but it's not deployed yet. This should happen by the end of today (CEST timezone).

@ghuntley
Copy link
Contributor

Resolved and in production.

@ChristianHuff-DEV
Copy link

@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)

@Menzorg
Copy link

Menzorg commented Aug 26, 2021

Indeed. We have problem with 15, but cant recreate our repo in 16 - all times it creates on 15.

@ivansglazunov
Copy link

ivansglazunov commented Aug 26, 2021

Resolved and in production.

Not resolved. Every time eu15, and every time error.

@csweichel
Copy link
Contributor

/schedule

@roboquat
Copy link
Contributor

@csweichel: Cannot schedule issue - issue does not belong to a team. Use /team to specify one.

In response to this:

/schedule

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.

@csweichel
Copy link
Contributor

/team workspace

@roboquat roboquat added the team: workspace Issue belongs to the Workspace team label Aug 27, 2021
@csweichel
Copy link
Contributor

/schedule

@roboquat
Copy link
Contributor

@csweichel: Issue scheduled in the workspace team (WIP: 0)

In response to this:

/schedule

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.

@csweichel
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
groundwork: awaiting deployment priority: highest (user impact) Directly user impacting team: workspace Issue belongs to the Workspace team type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants