Containers · Operations
Linux & Docker Services
A multi-service Docker environment used for deploying, observing, and troubleshooting applications without mixing those services with the public website.
Project overview
Containerized services in the homelab include a media stack, local tools, and supporting utilities. Docker makes it possible to separate application processes while still sharing a host operating system.
Services explored
- Media: Jellyfin and Plex, with related library-management services.
- Operations: container health checks, logs, port mappings, and restart policies.
- Web tools: a self-hosted start page and local web applications.
- Networking: container bridge networks and services that use a VPN-linked container.
Troubleshooting approach
- Check container state with
docker psand inspect unhealthy services. - Examine recent logs for actionable errors.
- Confirm which ports are bound to the host and which stay inside Docker networks.
- Test connectivity from the right network namespace before changing settings.
- Make one change at a time and retest.
Lessons learned
Container networking is not identical to host networking. A service bound to 127.0.0.1 on the host is not reachable at that address from a container using the default bridge network. Understanding namespaces and port bindings is essential for correct troubleshooting.
Add curated screenshots or logs with identifiers and credentials removed, and document results from future experiments.