-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
ubuntu-24.04 Error during unshare(...): Operation not permitted #10443
Comments
@Raboo - Thank you for bringing this issue to our attention. We will look into this issue and will update you on this issue after investigating. |
Hi @Raboo - The error you're encountering with skopeo copy on Ubuntu 24.04 is related to the unprivileged user namespace (unshare) being restricted in the latest Ubuntu versions. This restriction is likely causing the "Operation not permitted" error when skopeo tries to use unshare. I am providing workaround for you below: Workarounds and Solutions A. Enable User Namespace Remapping Add the following line to /etc/sysctl.conf: Then apply changes as:- This might not be an option if you're using a CI runner where you don't have root access. B. Run skopeo in a Privileged Container Here’s how you could modify your workflow:
C. Switch to Podman You can install and use podman like so:
D. Revert to Ubuntu 22.04 So, overall the "Operation not permitted" error with skopeo on Ubuntu 24.04 is due to restrictions on user namespaces. You can enable the necessary kernel parameter, run skopeo in a privileged container, switch to podman, or revert to Ubuntu 22.04 as potential workarounds. |
@Prabhatkumar59 I opted for the
Thanks! |
…ers (#2010) Summary: Another attempt to remediate user namespace issues with ubuntu 24.04 runners This reverts the failed previous attempt and re-enables user namespaces on ubuntu 24.04. This is a well known behavior change between Ubuntu 22.04 and 24.04 (actions/runner-images#10443 (comment)). Since podman is running rootless, I think it's possible that the user namespace creation (clone syscall) is failing. Relevant Issues: #1993 Type of change: /kind bugfix Test Plan: Run another production release build after merging this - Verified that this sysctl cli invocation is similar to our [existing example](https://github.com/pixie-io/pixie/blob/aa1f72a69f0a072d97accd721081f89cb8108fd1/.github/workflows/build_and_test.yaml#L87) --------- Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Description
I have a problem with this new ubuntu runner.
This is something that worked on 22.04.
Now instead it produces an error.
Platforms affected
Runner images affected
Image version and build link
I can't find this "Set up job" button anywhere.
I used yaml to create the action.
https://github.com/Raboo/redir/actions
Is it regression?
don't know
Expected behavior
skopeo copy
should not produce an error.Actual behavior
Getting an unshare error.
Repro steps
Build an image with redhat-actions/buildah-build.
try to copy the image to a tar archive like so
skopeo copy containers-storage:ghcr.io/${{ env.OWNER_LC }}/redir:build-${{ env.PODMAN_ARCH }} oci-archive:/tmp/${{ env.PODMAN_ARCH }}-oci.tar
The text was updated successfully, but these errors were encountered: