Overview
A good chunk of my lab runs on docker. My joplin, flame, and jellyfin servers are all docker containers. With docker you can easily create and run services, with or without a compose file. Docker containers are easy to replicate and scale(horizontally) too, thanks to Compose.
Why Docker?
- Completely free and Open-Source
- Trusted in many production environments
- Easy replication with compose
- Extremely stable
- very lightweight
Key Features
- Containerization
- portability
- Scalability
- Easy deployment
- Networking - internal networks
Basic Jellyfin image pull
Example of Jellyfin image pull
docker run command for jellyfin
Run this command after you have already created you jellyfin config and cache directories. This command will create and start the container.
Use Cases
- Any container
- Small applications
- Home lab projects
- Development
Future Improvements
- More services!
- Configuring automated scaling
- Adding more hardware resources
My Thoughts & Opinions
Docker was the correct option for me. Since I first started learning about computers, virtualization has always seemed like magic to me. Containers, while they function and are created differently, have the same feel. Weather it's me messing up and needing to nuke something or me just playing around and learning, docker has me covered.
The ease of use is one reason I would recommend it to beginners. If you haven't used it, give it a shot, you're missing out.