🐳 Docker Services
Designed and deployed multiple Docker services for home security camera streaming, service discovery, and reverse proxy management, managed through Portainer while learning containerized application deployment.
Overview
Running services in Docker containers on top of the Proxmox home lab gave me a practical way to learn containerized deployment without risking a full VM rebuild every time something went wrong. Each service runs in its own container, defined and versioned through Docker Compose so the whole stack can be torn down and rebuilt from a single file.
I manage the stack through Portainer for a clear view of container state, published ports, and images at a glance. go2rtc handles low-latency streaming for my home security cameras, Nginx Proxy Manager takes care of reverse proxy routing, and Homepage acts as a central launcher for everything running in the lab.
Technologies Used
- Docker
- Docker Compose
- Nginx Proxy Manager
- Homepage
- Portainer
- go2rtc
Highlights
- Deployed a Homepage dashboard to monitor and launch all self-hosted services.
- Run go2rtc for low-latency streaming of home security cameras.
- Used Nginx Proxy Manager to route traffic to each service over clean subdomains.
- Manage the full container stack through Portainer.
- Defined every stack with Docker Compose for repeatable, version-controlled deployments.
Challenges
- Understanding Docker's default bridge networking versus custom networks.
- Managing persistent volumes so container updates didn't wipe data.
- Getting reverse proxy and SSL configuration right in Nginx Proxy Manager.
- Keeping container images updated without breaking working configs.
What I Learned
This project taught me how containerized applications are structured, networked, and persisted, and gave me real practice with Docker Compose as a way to document and reproduce a deployment instead of configuring services by hand each time.