Why interacting with containers matters in Docker - Visual Breakdown

Process Flow - Why interacting with containers matters

Start Container

↓

Container Running

↓

Interact: Exec Command

↓

See Output / Change State

↓

Stop or Continue Container

↓

Exit or Repeat Interaction

This flow shows how starting a container leads to running it, then interacting by executing commands inside it, observing results, and deciding to stop or continue.

Execution Sample

Docker

docker run -it ubuntu bash
# Inside container
ls /
exit

Starts an Ubuntu container interactively, lists root directory contents inside it, then exits the container.

Process Table

Step	Action	Command	Result / Output	Container State
1	Start container interactively	docker run -it ubuntu bash	Container shell prompt appears	Running
2	Execute command inside container	ls /	bin boot dev etc home lib media mnt opt proc root run sbin srv sys tmp usr var	Running
3	Exit container shell	exit	Container stops	Exited

💡 Container stops after exit command ends the interactive session

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
Container State	Not running	Running	Running	Exited
Command Output	None	Shell prompt	List of root files/folders	None

Key Moments - 2 Insights

Why do we need to interact with a running container instead of just starting it?

Interacting lets us run commands inside the container to check or change its state, as shown in step 2 of the execution_table where 'ls /' lists files inside.

What happens if we exit the container shell?

Exiting the shell stops the container, as shown in step 3 where the container state changes to 'Exited'.

Visual Quiz - 3 Questions

Look at the execution_table, what is the container state after running 'ls /'?

A Paused

B Running

C Stopped

D Exited

💡 Hint

Check the 'Container State' column at step 2 in the execution_table.

At which step does the container stop running?

A Step 1

B Step 2

C Step 3

D Never stops

💡 Hint

Look at the 'Container State' column and see when it changes to 'Exited'.

If we skip the 'exit' command, what would happen to the container state?

A It remains running

B It stops automatically

C It crashes

D It pauses

💡 Hint

Refer to the variable_tracker for 'Container State' after step 2 and step 3.

Concept Snapshot

docker run -it image command
- Starts container interactively
- Lets you run commands inside
- Interaction changes container state
- Exiting shell stops container
- Useful for debugging and control

Full Transcript

When you start a container with 'docker run -it', you get an interactive shell inside it. You can run commands like 'ls /' to see files inside the container. This interaction helps you check or change the container's state. When you type 'exit', the container stops running. Interacting with containers matters because it lets you control and debug them live.