-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Can't sudo in a container #126
Comments
sudo is not installed in the container you do not need to use it to apt-get On Tue, Jul 14, 2015 at 4:36 PM, yakbulut notifications@github.com wrote:
|
On Tue, Jul 14, 2015 at 04:38:49PM -0700, Jessie Frazelle wrote:
I don't think that's the problem (if it was, @yakbulut would be
PERM_SUDOERS seems to be a SELinux permission 1. I'm not sure how |
On Tue, Jul 14, 2015 at 04:38:49PM -0700, Jessie Frazelle wrote:
^ this part I agree with ;). |
I know for a fact in that rootfs it is not installed On Tue, Jul 14, 2015 at 4:49 PM, W. Trevor King notifications@github.com
|
jk its not debian, i take that back On Tue, Jul 14, 2015 at 4:56 PM, Jessie Frazelle jess@docker.com wrote:
|
My first impression was that it was related to sudo. If try
Here is linux capabilities. Am I missing something here ?
|
On Tue, Jul 14, 2015 at 05:04:17PM -0700, yakbulut wrote:
Have you mounted your /etc/shadow read-only? Maybe stracing that EXIT VALUES so I suspect a mount-access or permissions issue. |
Hi all, Thanks for all the tips. It turns out that I had to include bunch of linux capabilities. |
Hi all,
I am trying to run a service, i.e mysql, inside a container. I gathered the ubuntu rootfs from docker pull ubuntu:latest.
Although
whoami
returnsroot
, sudo command fails withsudo: PERM_SUDOERS: setresuid(-1, 1, -1): Operation not permitted
As a result, I can't apt-get install or do any other sudo tasks.
How can I get around this issue?
Thanks in advance,
The text was updated successfully, but these errors were encountered: