Mastering Attached and Detached Modes

Welcome back! In previous lessons, you've become adept at managing Docker containers, including creating custom images and configuring port mappings. Today, we'll delve into the concept of execution modes, a vital component of gaining full control over container operations. In Docker, execution modes determine how a container interacts with your terminal session. The two primary modes are attached and detached . Understanding and effectively using these modes can significantly enhance your control over container processes, whether you're debugging a live system or deploying an application to run independently. By the end of this lesson, you'll be able to execute Docker containers in both attached and detached modes using specific commands, setting the groundwork for more advanced Docker operations.

Understanding Attached Mode

Let's begin with attached mode. When you run a container in attached mode, the container's standard input, output, and error streams are connected to your terminal session. This means you can see everything happening inside the container in real-time. It's like sitting in front of a computer and watching the screen as programs run. Attached mode is beneficial when you need to monitor logs, debug issues, or interactively work with the application inside the container. For example, if you were running an Nginx server in attached mode, you might observe real-time log messages such as: text /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh 10-listen-on-ipv6-by-default.sh: info: IPv6 listen already enabled /docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh /docker-entrypoint.sh: Configuration complete; ready for start up 2024/10/16 13:54:44 [notice] 1#1: using the "epoll" event method 2024/10/16 13:54:44 [notice] 1#1: nginx/1.27.2 2024/10/16 13:54:44 [notice] 1#1: built by gcc 12.2.0 (Debian 12.2.0-14) 2024/10/16 13:54:44 [notice] 1#1: OS: Linux 6.5.0-1018-aws 2024/10/16 13:54:44 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576 2024/10/16 13:54:44 [notice] 1#1: start worker processes ... This output confirms that the Nginx configuration has been successfully processed, and the server is ready to handle requests.

Join the 1M+ learners on CodeSignal

Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal

text

884fda246c7aec578f8476c6d96a602f518eda6869047c08ecf2560bfda92d78

884fda246c7aec578f8476c6d96a602f518eda6869047c08ecf2560bfda92d78

Shell

# Run a container in attached mode (default)
docker run nginx

# Run a container in attached mode (default)
docker run nginx

Shell

# Run a container in detached mode
docker run -d nginx

# Run a container in detached mode
docker run -d nginx

Shell

# Start an existing container in detached mode (default)
docker start <container-id-or-name>

# Start an existing container in detached mode (default)
docker start <container-id-or-name>

Shell

# Start an existing container in attached mode
docker start -a <container-id-or-name>

# Start an existing container in attached mode
docker start -a <container-id-or-name>

Shell

# View logs of a container identified by container ID or name
docker logs <container-id-or-name>

# View logs of a container identified by container ID or name
docker logs <container-id-or-name>

Shell

# Continuously monitor logs in real-time
docker logs -f <container-id-or-name>

# Continuously monitor logs in real-time
docker logs -f <container-id-or-name>

Shell

# Run a container in detached mode with port mapping and a specific name
docker run -d -p 8080:80 --name my-nginx nginx

# Run a container in detached mode with port mapping and a specific name
docker run -d -p 8080:80 --name my-nginx nginx

text

884fda246c7aec578f8476c6d96a602f518eda6869047c08ecf2560bfda92d78

Shell

# Run a container in attached mode (default)
docker run nginx

Shell

# Run a container in detached mode
docker run -d nginx

Shell

# Start an existing container in detached mode (default)
docker start <container-id-or-name>

Shell

# Start an existing container in attached mode
docker start -a <container-id-or-name>

Shell

# View logs of a container identified by container ID or name
docker logs <container-id-or-name>

Shell

# Continuously monitor logs in real-time
docker logs -f <container-id-or-name>

Shell

# Run a container in detached mode with port mapping and a specific name
docker run -d -p 8080:80 --name my-nginx nginx

Mastering Attached and Detached Modes

Understanding Attached Mode

Join the 1M+ learners on CodeSignal

Understanding Detached Mode

Executing Containers with Docker Run

Executing Containers with Docker Start

Viewing Logs of Containers in Detached Mode

Combining Different Flags

Common Questions and Doubts

Summary and Preparation for Practice