Hands-on task
The wrong neighbor address in environment variables
The storefront frontend in the store network is published on the server's 127.0.0.1:8080, and curl http://127.0.0.1:8080/call answers 502: the storefront can't reach the catalog. The catalog container itself is alive.
The storefront takes the catalog's address from UPSTREAM in /root/frontend/frontend.env. Find out which name and port the catalog is actually reachable at, fix the env file and recreate frontend with the same name, network, 127.0.0.1:8080 publishing and this env file. Don't touch catalog — you may not recreate or restart it.
The lab has its own Docker with no internet access; the images are already loaded: izzylab/minihttp:1, alpine:3.21, busybox:1.36, nginx:1.27-alpine. izzylab/minihttp is a tiny HTTP service on port 8080: GET / answers <NAME> ok, GET /call itself goes to http://<UPSTREAM>/ and answers <NAME> -> <the neighbor's reply> (or 502), GET /env shows its settings. It is configured with the environment variables NAME, PORT, BIND (the address it listens on) and UPSTREAM.
- docker inspect
- docker logs
- environment variables