I'm looking to set up a separate VM just for my Samba server. While I know Docker can accomplish this, it seems like simply installing the package directly might be easier, especially since the VM will only be running Samba. Any thoughts on the pros and cons? Also, I plan to use either Proxmox or ESXi as the hypervisor, though running Samba in a container isn't my first choice.
5 Answers
One big plus for Docker is that installing it directly can clutter your system with config files and libraries scattered everywhere. With Docker, when you remove a container, it clears everything associated with it, which is super clean and convenient.
Docker eliminates a lot of dependency headaches. You don’t have to stress about making sure Python, Node.js, Java, etc., are all correctly set up for the app—Docker handles that for you.
Using Docker makes deployment simple with a compose file, and it keeps your system clean. You can run versions of libraries that might differ from your system's, allowing for more flexibility.
If you’re just using Samba for Active Directory, then a Docker container is a good choice since it's lightweight. But if you're setting it up primarily for file sharing, the VM route might be better.
Using Docker is pretty much like having a mini VM solely for one app, which means it's more efficient with resources compared to a full VM setup. You're not wasting CPU and RAM on extra services that won't be used.
That's true, but remember that a VM requires more maintenance, like regular updates and patches. With a Samba container, you can just swap versions easily without worrying about issues.