The root cause of the sudo: effective uid is not 0, is /usr/sbin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges? error is explained in https://github.com/multiarch/qemu-user-static/issues/17.
In summary the QEMU Docker instance needs to launched so the binfmt_misc flags include OCF. Prior to this PR the flags are limited to F, which can be confirmed using following run-on-arch-action configuration:
This PR resolves issue #68.
The root cause of the
sudo: effective uid is not 0, is /usr/sbin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?
error is explained in https://github.com/multiarch/qemu-user-static/issues/17.In summary the QEMU Docker instance needs to launched so the
binfmt_misc
flags includeOCF
. Prior to this PR the flags are limited toF
, which can be confirmed using followingrun-on-arch-action
configuration:This returns:
Applying the PR results in:
sudo
now works inrun-on-arch-action
containers.