If the docker container root directory has the nosuid flag set on the mount, the use of sudo within the container initialisation script fails. The container reports as being successfully initialised but within the console output is the following, indicating that it has not been successful.
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?
The fix is to remove the nosuid flag on the mount - a defensive measure within the zdm util script and proxy deployment script would be to check this flag before progressing.
┆Issue is synchronized with this Jira Task by Unito
┆Components: Automation
┆Priority: Major
If the docker container root directory has the nosuid flag set on the mount, the use of sudo within the container initialisation script fails. The container reports as being successfully initialised but within the console output is the following, indicating that it has not been successful.
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?The fix is to remove the nosuid flag on the mount - a defensive measure within the zdm util script and proxy deployment script would be to check this flag before progressing.
┆Issue is synchronized with this Jira Task by Unito ┆Components: Automation ┆Priority: Major