Skip to content

Conversation

@msimberg
Copy link
Collaborator

@msimberg msimberg commented Apr 7, 2025

No description provided.

@msimberg msimberg requested review from RMeli and bcumming as code owners April 7, 2025 14:18
@msimberg msimberg force-pushed the failed-to-unshare-mount branch from fa45034 to cf0ed0b Compare April 7, 2025 14:19
@github-actions
Copy link

github-actions bot commented Apr 7, 2025

preview available: https://docs.tds.cscs.ch/78

1 similar comment
@github-actions
Copy link

github-actions bot commented Apr 7, 2025

preview available: https://docs.tds.cscs.ch/78

Copy link
Member

@RMeli RMeli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM and much needed!

The only issue is that searching for "Failed to unshare the mount namespace" or "squashfs-mount: Failed to unshare the mount namespace: Operation not permitted" doesn't seem to hit this warning.

@msimberg
Copy link
Collaborator Author

msimberg commented Apr 7, 2025

The only issue is that searching for "Failed to unshare the mount namespace" or "squashfs-mount: Failed to unshare the mount namespace: Operation not permitted" doesn't seem to hit this warning.

Oof, that's very unfortunate. I just checked, and for some reason it seems to show up with a plain unshare search.

Edit: It also seems to show up with "failed to unshare", i.e. when wrapped in quotes. Bad in any case...

@RMeli RMeli merged commit 113574a into eth-cscs:main Apr 8, 2025
1 check passed
@msimberg msimberg deleted the failed-to-unshare-mount branch April 10, 2025 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants