How to fix this issue? sudo: The "no new privileges" flag is set, which prevents sudo from running as root. sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.

EMMANUEL 1

Please how do I fix this error on an Ubuntu Linux running in Azure VM?
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.

sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.

Akshay kumar Mandha 385 Reputation points Microsoft Vendor

2024-09-03T18:59:07.0433333+00:00

Hi EMMANUEL,
Welcome to the Microsoft Q&A Platform.
Thank you for posting your query here. We are looking into it and will get back to you soon.
Rafael Mendonça 0 Reputation points

2024-09-03T20:09:55.42+00:00

Getting the same error =(
Dion Whitehouse 0 Reputation points

2024-09-04T04:44:37.5033333+00:00

I have this exact same issue
manish nahar 0 Reputation points

2024-09-11T07:54:38.27+00:00

Same issue. no docker installed. just fresh VM created with Linux (ubuntu 24.04) and getting same error of "no new privileges" flag

1 answer

Akshay kumar Mandha 385 Reputation points Microsoft Vendor

2024-09-04T14:53:30.54+00:00
Hi EMMANUEL,
Thank you for your patience while we are reviewing the issue

Based upon your query, If the ubuntu linux VM in azure is running inside a container you need adjust the container's security setting to disable the "no new privileges" flag. If it is docker containers, use the below command

docker run --security-opt no-new-privileges = false

Optionally when starting the container, or update your docker compose file to include below config

services: your_service: image: your_image security_opt: - no-new-privileges=false

For Kubernetes or other container environments, update the pod security policies or security context to allow privilege escalation. If an answer has been helpful, please consider accepting the answer and "Upvote" to help increase visibility of this question for other members of the Microsoft Q&A community.
Please sign in to rate this answer.
Akshay kumar Mandha 385 Reputation points Microsoft Vendor

2024-09-05T15:02:17.15+00:00

Hi EMMANUEL,
I wanted to follow up If you had chance to please review my answer If it is resolve your issue, Please upvote and accept my answer on posted the solution. For better other community will visible and helpful.
Thank you..!

Akshay kumar Mandha 385 Reputation points Microsoft Vendor

2024-09-05T17:20:49.16+00:00

Hi EMMANUEL,
Just checking to see If you had chance to please review my answer If it is resolve your issue, Please upvote and accept my answer on posted the solution. For better other community will visible and helpful.
Thank you..!

Stefan N. Lukianov 0 Reputation points

2024-09-07T15:25:14.42+00:00

Hi Akshay,

I had the same problem as Emmanuel, and when I tried your suggestion of the docker command, my terminal reported the command not found. How do I determine what container my Ubuntu VM is running in to change its configuration and enable the sudo command? Thanks very much.

Stefan

Stefan N. Lukianov 0 Reputation points

2024-09-07T15:27:57.45+00:00

Hi Akshay,

I had the same problem as Emmanuel and when I tried your suggestion it said the docker command is not found. How do we determine our container to enable the sudo command? Thanks very much.

Stefan

Akshay kumar Mandha 385 Reputation points Microsoft Vendor

2024-09-09T13:05:24.48+00:00

Hi Stefan N. Lukianov,

Based upon query, you can try this once below steps one by one run the command to resolve the issue

First ensure Docker is installed by checking its version with docker --version. Then, inspect your running containers using docker ps and get details with docker inspect <container_id>. If sudo is not functioning, you need to start the container with the --security-opt no-new-privileges=false option. You can do this by running docker run --security-opt no-new-privileges=false your_image. Alternatively, if you use Docker Compose, add this security option to your docker-compose.yml file under the security_opt section. After applying these changes, restart your container and check if sudo works correctly.

If you found this helpful, Please click an "Upvote" and "accept the answer" on my post. For better other community will be visible.

Thank you..!

Stefan N. Lukianov 0 Reputation points

2024-09-10T16:55:33.7866667+00:00

The docker command doesn't work because docker isn't installed, and I can't install it because the sudo command won't work. What should I do to adjust the permissions if I don't know the container?

Akshay kumar Mandha 385 Reputation points Microsoft Vendor

2024-09-10T17:31:04.3466667+00:00

Hi Stefan N. Lukianov,
Thank you for getting back to us We are looking into it and will get back to you soon.

Akshay kumar Mandha 385 Reputation points Microsoft Vendor

2024-09-11T10:08:59.17+00:00

Hi Stefan N. Lukianov,
Based upon your query, Please do refer the below document
How To Create A New Sudo Enabled User on Ubuntu
How to Know if a User has Sudo Rights
Could you please provide more info on this better we can assist you If the above document is helpful for you please click "Upvote" on this comment
Thank you..!

Stefan N. Lukianov 0 Reputation points

2024-09-11T15:04:20.8133333+00:00

Thanks, when I try to add a new Sudo user, the terminal returns "Permission Denied", and when I check Sudo rights, my username doesn't have them.

Stefan N. Lukianov 0 Reputation points

2024-09-11T15:20:18.96+00:00

I also noticed that when I logon to the cloud shell, I get this output:

stefan [ ~ ]$ az ssh vm --resource-group Salve_Therapeutics --vm-name Salve-GPU2.0 --subscription 3e83634d-1870-4f5d-aea5-6ec28da9f6d3

OpenSSH_8.9p1, OpenSSL 1.1.1k FIPS 25 Mar 2021

stefanlukianov@salvetherapeutics.onmicrosoft.com@20.127.67.177: Permission denied (publickey).

How do I grant myself permission? I think that's the root problem. Thanks!

Akshay kumar Mandha 385 Reputation points Microsoft Vendor

2024-09-12T10:44:43.95+00:00

Hi Stefan N. Lukianov,
Thank you for getting back to us
Can you try once by creating the VM with username and password instead of private key authentication, Check the issue still persists or not.!
If is helpful for you please click an "Upvote" on this comment
Thank you..!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to fix this issue? sudo: The "no new privileges" flag is set, which prevents sudo from running as root. sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.

1 answer

Your answer