Containerization & Orchestration on Raspberry Pi Practice Te

In the context of Docker on Raspberry Pi, what is the primary advantage of using multi-stage builds for creating Docker images, particularly when dealing with resource-constrained environments?

When deploying a containerized application on a Raspberry Pi using Docker Compose, what is the most effective strategy to ensure that a sensitive configuration file (e.g., database credentials) is securely injected into the container without being hardcoded in the Dockerfile or visible in the compose file?

Consider a scenario where you are running multiple Docker containers on a Raspberry Pi, and one container (e.g., a web server) needs to communicate with another container (e.g., a database) using their service names. What is the underlying Docker networking mechanism that enables this name resolution by default when using Docker Compose?