Seems like `ubuntu:14.04` image has no setuid bit set on `/usr/bin/sudo` about docker-brew-ubuntu-core

[gstib]

I'm also seeing this, only started happening last night

Error running 'requirements_debian_update_system ',
showing last 15 lines of /home/rails/.rvm/log/1411597891/update_system.log
+ [[ -d /usr/sbin ]]
+ [[ ! :/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/rails/.rvm/bin: =~ :/usr/sbin: ]]
+ for sbin_path in /sbin /usr/sbin /usr/local/sbin
+ [[ -d /usr/local/sbin ]]
+ [[ ! :/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/rails/.rvm/bin: =~ :/usr/local/sbin: ]]
+ [[ -n '' ]]
+ command_to_run=(__rvm_sudo -p "%p password required for '$*': " "${command_to_run[@]}")
+ __rvm_sudo -p '%p password required for '\''apt-get --quiet --yes update'\'': ' apt-get --quiet --yes update
+ command sudo -p '%p password required for '\''apt-get --quiet --yes update'\'': ' apt-get --quiet --yes update
+ sudo -p '%p password required for '\''apt-get --quiet --yes update'\'': ' apt-get --quiet --yes update
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
+ return 1
+ typeset __ret=1
+ case ${__ret} in
+ return 1
Requirements installation failed with status: 1.

[gstib]

Temp fix is to run these two commands

RUN chown root:root /usr/bin/sudo
RUN chmod 4755 /usr/bin/sudo

[burke]

Yup, we found this too; had to add chmod 4755 /usr/bin/sudo in our buildscripts.

[tianon]

While this appears to be fixed in the latest images we've got up, I am very
curious to know what "sudo" is being used for "in the wild" (so to speak)
in Docker containers. Anyone care to elaborate?

(Also, please "docker pull ubuntu:14.04" and verify that the setuid bit is
set properly now.)

[burke]

We have a baseimage which creates a user (let's say user), sets the default user of the image to user, and gives user passwordless sudo rights.

Later, when we're building application images from this baseimage, we run a script in the application source tree, which may use sudo to, for example, install additional packages. After running this script, we revoke sudo rights from user and commit as our application image.

The reason this script runs as user and not root is so that any files created default to an ownership that's more compatible with our runtime user.

(Also, we removed our workaround for this some time ago, IIRC, it's been working fine).

[Nimeshka]

This happens when the permissions get changed. You can boot into Ubuntu recover mode and enter the following commands to get the root access back.

mount -o remount,rw /
mount --all
chown root:root /usr/bin/sudo
chmod 4755 /usr/bin/sudo
restart

source : http://bitmapcake.blogspot.com/2014/08/linux-fixing-error-sudo-usr-bin-sudo-must-be-owned-by-uid.html

[Nikhilchopada]

i am apply this command but its not work for me..so give me another solution
i use this command
mount -o remount,rw /
mount --all
chown root:root /usr/bin/sudo
chmod 4755 /usr/bin/sudo
restart