How to Use sudo Inside a Docker Container?

When working with Docker, you might sometimes want to use sudo inside a container, especially if you’re trying to mimic a traditional Linux environment.

However, by default, many Docker images don’t include sudo at all — and you usually don’t need it. Let’s break down why and how you can properly use sudo inside a container if you really need it.

Table of Contents

Why sudo Is Rarely Needed in Containers

Unlike a typical Linux system where you switch between normal users and root using sudo, containers are often designed to run processes directly as the root user. This makes sudo unnecessary in many cases because:

The container is isolated from your host system.
If you need elevated privileges, you usually run the container with root.
Best practice is to create specific users in Dockerfiles rather than relying on sudo.

That said, there are valid scenarios where you might want to add sudo inside a container, especially during development or for testing environments.

Installing sudo in a Container

If you really need sudo, you must first install it because most base images (like Debian, Ubuntu, Alpine) don’t include it by default.

Example: Ubuntu/Debian-based Container

FROM ubuntu:20.04

# Install sudo
RUN apt-get update && apt-get install -y sudo

# Create a new user and add to sudo group
RUN useradd -m dockeruser && \
    echo "dockeruser:password" | chpasswd && \
    adduser dockeruser sudo

USER dockeruser
WORKDIR /home/dockeruser

This creates a user named dockeruser.
Adds it to the sudo group.
Sets the default user for the container.

When you run the container, you can now use:

sudo apt-get update

Using sudo with Alpine Linux

Alpine doesn’t have sudo by default. You can install it with:

FROM alpine:latest

RUN apk add --no-cache sudo shadow

RUN useradd -m dockeruser && \
    echo "dockeruser ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers

USER dockeruser

Here, the dockeruser can run commands with sudo without requiring a password.

Best Practices Instead of sudo

While you can add sudo, most Docker experts recommend alternative approaches:

Use the root user in development: Since the container is isolated, it’s usually safe.
Switch to a non-root user in production: Define users with the USER instruction in your Dockerfile to limit privileges.
Run privileged tasks during build: Install software and configure the system in your Dockerfile instead of interactively using sudo later.

Conclusion

By default, Docker containers don’t include or need sudo. If your workflow requires it, you can install and configure it by creating a non-root user and giving them sudo privileges.

However, in most cases, structuring your Dockerfile properly and using USER directives is a cleaner and safer approach than relying on sudo inside containers.