Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sudo: effective uid is not 0 #744

Closed
henrik-farre opened this issue Dec 7, 2018 · 0 comments · Fixed by #745
Closed

sudo: effective uid is not 0 #744

henrik-farre opened this issue Dec 7, 2018 · 0 comments · Fixed by #745

Comments

@henrik-farre
Copy link

henrik-farre commented Dec 7, 2018

If I build this simple Docker file with buildkit enabled it fails:

FROM quay.io/ansible/molecule:latest

RUN sudo pip install --no-cache-dir pyvmomi \
  && sudo pip install --upgrade ansible[azure]

The error is:

> [2/2] RUN sudo pip install --no-cache-dir pyvmomi   && sudo pip install --upgrade ansible[azure]:
#5 0.603 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?
------
executor failed running [/bin/sh -c sudo pip install --no-cache-dir pyvmomi   && sudo pip install --upgrade ansible[azure]]: exit code: 1

Docker version is: 18.09.0-ce

Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: false
Runtimes: runc
Default Runtime: runc

Buildkit is enabled by export DOCKER_BUILDKIT=1

Note: I found the an existing bug report here: moby/moby#36730 but I think it might be more correct here?

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 a pull request may close this issue.

1 participant