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

"No usable sandbox" error when running on ubuntu-24.04 image #32

Closed
sschuberth opened this issue Dec 10, 2024 · 5 comments · Fixed by #34
Closed

"No usable sandbox" error when running on ubuntu-24.04 image #32

sschuberth opened this issue Dec 10, 2024 · 5 comments · Fixed by #34
Labels
bug Something isn't working

Comments

@sschuberth
Copy link

sschuberth commented Dec 10, 2024

Describe the bug

The action does not complete but gives

No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

To Reproduce

See this workflow.

Expected behavior

Linkspector should be able to run as part of the action.

Screenshots

image

Additional context

I'm trying to migrate from the gaurav-nelson/github-action-markdown-link-check action.

@sschuberth sschuberth added the bug Something isn't working label Dec 10, 2024
@sschuberth sschuberth changed the title "No usable sandbox" error "No usable sandbox" error when running on ubuntu-24.04 image Dec 10, 2024
@sschuberth
Copy link
Author

A work-around is to downgrade from ubuntu-latest / ubuntu-24.04 to ubuntu-22.04.

sschuberth added a commit to oss-review-toolkit/ort that referenced this issue Dec 10, 2024
The action for markdown-link-check is not maintained anymore, and the
underlying NPM package as several issues. So give the action [1] for
Linkspector [2] a try instead.

Note that due to [3] the action needs to run on `ubuntu-22.04`.

[1]: https://github.com/UmbrellaDocs/action-linkspector
[2]: https://github.com/UmbrellaDocs/linkspector
[3]: UmbrellaDocs/action-linkspector#32

Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
sschuberth added a commit to oss-review-toolkit/ort that referenced this issue Dec 10, 2024
The action for markdown-link-check is not maintained anymore, and the
underlying NPM package has several issues. So give the action [1] for
Linkspector [2] a try instead.

Note that due to [3] the action needs to run on `ubuntu-22.04`.

[1]: https://github.com/UmbrellaDocs/action-linkspector
[2]: https://github.com/UmbrellaDocs/linkspector
[3]: UmbrellaDocs/action-linkspector#32

Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
sschuberth added a commit to oss-review-toolkit/ort that referenced this issue Dec 11, 2024
The action for markdown-link-check is not maintained anymore, and the
underlying NPM package has several issues. So give the action [1] for
Linkspector [2] a try instead.

Note that due to [3] the action needs to run on `ubuntu-22.04`.

[1]: https://github.com/UmbrellaDocs/action-linkspector
[2]: https://github.com/UmbrellaDocs/linkspector
[3]: UmbrellaDocs/action-linkspector#32

Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
damacus added a commit to sous-chefs/.github that referenced this issue Dec 11, 2024
@jharrell
Copy link

Having the same issue. Can confirm that downgrading to ubuntu-22.04 works.

Also going to try this recommendation: https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md#option-1_the-easiest-way

specifically running the command echo 0 | sudo tee /proc/sys/kernel/apparmor_restrict_unprivileged_userns prior to starting up reviewdog/linkspector

@rfay
Copy link

rfay commented Dec 26, 2024

ubuntu-24.04 is working for me at this point.

I was wrong, had to revert to 22.04

KStocky added a commit to KStocky/ShaderTestFramework that referenced this issue Dec 27, 2024
@KStocky
Copy link

KStocky commented Dec 27, 2024

This issue has just started happening for me with ubuntu-24.04. See my run here Specifying ubunutu-22.04 did indeed "solve" the problem. This still needs to be fixed.

Realiserad added a commit to Realiserad/fish-ai that referenced this issue Dec 30, 2024
Linkspector fails on Uubntu 24.04 with the error message "No usable sandbox!". See UmbrellaDocs/action-linkspector#32
Realiserad added a commit to Realiserad/fish-ai that referenced this issue Dec 30, 2024
Linkspector fails on Uubntu 24.04 with the error message "No usable sandbox!". See UmbrellaDocs/action-linkspector#32
@lbussell lbussell moved this to Tracking in .NET Docker Jan 6, 2025
mikavilpas added a commit to mikavilpas/blink-ripgrep.nvim that referenced this issue Jan 9, 2025
mikavilpas added a commit to mikavilpas/blink-ripgrep.nvim that referenced this issue Jan 9, 2025
@rfay
Copy link

rfay commented Jan 21, 2025

Thanks for this! I assume we need a new release before we can move back to Ubuntu 24.04?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants