Check: containerizing | ComputeSphere Learn

Goal: Confirm you can design a health endpoint, read a containerizing Dockerfile's choices, and say what a Compose health condition waits for.

Four questions: three on Module 8 and one from Module 6. Every answer explains itself, right or wrong.

Your app can't serve any page without its database. What should /healthz do when the database is unreachable?Answer 503, saying the database is unreachableAnswer 200, since the process is runningWait until the database comes back, then answer 200

In a two-stage Dockerfile, the first stage runs npm ci or pip install, or compiles the code. Why not do that in the final image?The build tools would ship in the image you runIt makes the build fasterA single stage can't install dependencies

docker image inspect prints an empty User for an image you just built. What does that mean?The container will run as rootThe container has no user and can't startDocker will choose an unprivileged user when it starts

From Module 6: in compose.yaml, web has depends_on db with condition: service_healthy. What does web wait for?db's healthcheck to passOnly for the db container to startweb's own /healthz to answer 200

Retry as often as you like.