-
Notifications
You must be signed in to change notification settings - Fork 513
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
runtime/cgo: pthread_create failed: Operation not permitted #467
Comments
I'd suggest updating docker and libseccomp on the host. Newer base OS's use newer system calls and an older libseccomp can block them since they are unknown to it. You can verify that it is libseccomp by running the bookworm image with |
got the same issue using golang:1.20 since yesterday, some of operation not permitted
|
same issue here with golang:1.20.5 but golang:1.20.5-bullseye is working |
Same issue occured with golang:1.19 👀 Maybe it's because of this fix? |
Yep, definitely seccomp failures:
|
Root cause: it is Docker with
|
Sadly we were running a fairly recent OS everywhere except our CI machines. Guess it's time for an upgrade :) thanks for the explanation! Since this is related to the host machine and not the docker image I'm not sure how relevant this ticket is. I'll leave it open but feel free to close it out since it doesn't seem like their is anything to be done on the docker image side. |
sloved by upgrate to docker 20.10.24 |
Stuck with an older version of Docker, but switching to a "-bullseye" image (as suggested by @yosifkit above) solved the issue for us (for now). |
This comment was marked as spam.
This comment was marked as spam.
it really useful wen is upgrade the docker engine version to the newest. |
This comment was marked as spam.
This comment was marked as spam.
Had to switch to golang:1.20-bullseye base image and disable CGO in order to get the images to work on the target host when building on linux build hosts. See docker-library/golang#467
All of a sudden today in CI on the docker 1.20 image I am getting this error. In general the OS hasn't mattered to me since I'm not installing anything in the container however over the past week all of these bookworm upgrades have broken multiple things. This has been an absolute pain. I pinned back to bullseye to fix the issue.
The text was updated successfully, but these errors were encountered: