What is the effect of the -d flag when starting a container?

What is the effect of the -d flag when starting a container?

• A. Runs in interactive mode
• B. Detaches the container from the terminal and runs in the background
• C. Deletes the container after exit
• D. Enables privileged mode

Answer: (B)

Starting a container with this flag runs it in detached mode, meaning it starts and then continues to run in the background, not tied to your current terminal session. You won’t see the container’s output in the terminal, and you can close the terminal while the container keeps running. If you need to check what it’s doing, you can view logs later with commands like docker logs. This is different from interactive mode, which attaches your terminal to the container and lets you interact with its shell directly. The flag does not delete the container after it exits, nor does it enable privileged mode (those involve other options or capabilities).

Starting a container with this flag runs it in detached mode, meaning it starts and then continues to run in the background, not tied to your current terminal session. You won’t see the container’s output in the terminal, and you can close the terminal while the container keeps running. If you need to check what it’s doing, you can view logs later with commands like docker logs. This is different from interactive mode, which attaches your terminal to the container and lets you interact with its shell directly. The flag does not delete the container after it exits, nor does it enable privileged mode (those involve other options or capabilities).