Connect a Container to a Service Running on the Docker Host
Learn how to access services running on the Docker host from a bridge-networked container, without hardcoding host IP addresses or disabling network isolation.
Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.
Learn how to access services running on the Docker host from a bridge-networked container, without hardcoding host IP addresses or disabling network isolation.
Sometimes you need an app to talk to a different backend, but its configuration is unknown or the destination address is hard-coded. Practice overriding hostname resolution for a single Docker container to redirect its requests without modifying the app or rebuilding its image.
Explore the container networks of a freshly installed Docker host: find the default network, its subnet and gateway, and the Linux interface behind it.
A common setup for small deployments: two servers (VM or bare-metal), each with a public and a private IP. The app listens on the public port but wants to talk to Redis over the private network. Can you set it up?
Practice accessing a containerized service directly from the Docker host using its IP address.
Learn how to keep a database available to an app running on your workstation without exposing its port to other machines on the network.
A web app is listening inside a container, but the browser can't reach its IP address. Recreate the container so the app is available on port 80 of the Docker host.
Practice using docker login to authenticate against multiple private container registries with different credentials, then pull and push images across them.
Re-tag local container images with fully-qualified references and publish them to different registries using the 'docker tag' and 'docker push' commands.
Pull a container image built for a non-native CPU architecture using the 'docker pull --platform' flag.