-
Notifications
You must be signed in to change notification settings - Fork 757
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 #1501
Comments
Thanks for your report. Is this moby/moby#42680 ? |
I also see it here |
Preferably upgrade Docker, or change the seccomp policy, or I guess disable seccomp for these containers. |
@mtrmac thanks for the reply! AFAIK we're using the latest docker for fedora. what version should I use? [update] I meant |
Newer versions of the OS move to newer SYSCALLS, which older versions of Docker do not allow. |
I see, thank you for the response! :) |
Recent skopeo releaeses updated the OS and moved to use more advanced syscalls, ones that are currently filtered by docker (issue [0]). In order to move past this issue, moving to Podman. [0] containers/skopeo#1501 Signed-off-by: Ram Lavi <ralavi@redhat.com>
Recent skopeo releaeses updated the OS and moved to use more advanced syscalls, ones that are currently filtered by docker (issue [0]). In order to move past this issue, updating to image using fedora 34. [0] containers/skopeo#1501 Signed-off-by: Ram Lavi <ralavi@redhat.com>
Recent skopeo releaeses updated the OS and moved to use more advanced syscalls, ones that are currently filtered by docker (issue [0]). In order to move past this issue, updating to image using fedora 34. [0] containers/skopeo#1501 Signed-off-by: Ram Lavi <ralavi@redhat.com>
A friendly reminder that this issue had no activity for 30 days. |
@rhatdan and @mtrmac I get the same error on CentOS 7 with skopeo 1.7.0 using docker 20.10.16, so it doesn't seem that newer docker versions help here.
Using |
Issue is still present |
@venomone I’m not aware of anything changing in this area recently, and the over-a-year-old recommendation #1501 (comment) would apply to that old situation. If that’s not what you see, please file a new report with full details of the environment and the involved versions of all relevant components. |
Hit the same error, and upgrading docker to a newer version such as 20.10.21 worked for me. |
Hello
We started getting seccomp related errors when running
the errors appeared with 1.5.x, 1.4.1 is working fine.
The text was updated successfully, but these errors were encountered: