You can build images and store them in a registry. Now it's time to run them properly and to get containers talking to each other and to the outside world.
docker run creates and starts a container from an image, and a handful of flags cover most everyday use: -d runs it in the background, --name gives it a readable name, -e sets environment variables, and -p publishes a port. Once a container is running, docker ps, docker logs, docker exec, and docker stop let you inspect and manage it.
Networking decides who can reach what. Containers on the default bridge network are isolated from the host unless you publish a port, and custom networks let containers find each other by name. The host and none modes cover the remaining cases. Watch the lessons in order, then continue on to Container Security & Developer Experience.
How to create new containers with the docker run command, starting from the basics of what the command does.
A step-by-step walkthrough of the essential commands for running your first container and managing it afterwards.
A beginner-friendly introduction to how containers communicate, covering the bridge and host networks and how Compose sets up networking for you.
How the default bridge network works, and how to create custom networks so your containers can connect to each other.
A tour of every Docker network type, with guidance on when to use each one.