You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
Using sudo in a arm64 distrobox from an x86_64 host returns:
sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?
To Reproduce
Steps to reproduce the behavior
distrobox create --image debian:12 --name debian-12-arm --platform linux/arm64 --home /path/to/box/home
distrobox enter debian-12-arm
sudo
sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?
Expected behavior
A clear and concise description of what you expected to happen.
sudo working
Logs
Run the commands with --verbose and post the log here as a file upload
Attach also the output of podman logs or docker logs, possibly with --latest flag
Describe the bug
A clear and concise description of what the bug is.
Using sudo in a arm64 distrobox from an x86_64 host returns:
sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?
To Reproduce
Steps to reproduce the behavior
distrobox create --image debian:12 --name debian-12-arm --platform linux/arm64 --home /path/to/box/home
distrobox enter debian-12-arm
sudo
sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?
Expected behavior
A clear and concise description of what you expected to happen.
sudo working
Logs
Run the commands with
--verbose
and post the log here as a file uploadAttach also the output of
podman logs
ordocker logs
, possibly with--latest
flagpodman_log.txt
Desktop (please complete the following information):
podman 5.3.2
distrobox 1.8.1.2
arch linux
pacman -S distrobox
Additional context
Add any other context about the problem here.
my other x86_64 debian boxes work great
other commands work fine too in the box so qemu is doing its thing
The text was updated successfully, but these errors were encountered: