I just start using my homelab to host some new good services, and I want to know what is the approach of a docker setup, what is the best distro for? How to deploy them correctly? Basically I’m a real noob in this subject. Thank you
I just start using my homelab to host some new good services, and I want to know what is the approach of a docker setup, what is the best distro for? How to deploy them correctly? Basically I’m a real noob in this subject. Thank you
Debian with the docker convenience script. Stay away from Ubuntu server, for the love of dog.
Make a folder such as /stacks and put everything there by building docker compose stacks. I bind mount everything local to a subfolder with the docker-compose.yml for that application so when I restore it, it’s all in one spot, not spread all over the hell like docker likes to do if you don’t use bind mounts.
Add lazydocker for getting easy log and stats access for each stack.
They seem to be moving away from this, and it’s not longer the first option on their install page
On their debian page
Also, it should be noted about the first option they recommend, Docker Desktop, that Docker Desktop is proprietary.
I recommend just getting the
docker.ioanddocker-composefrom debian’s repositories.Well, that’s a new development. That used to be the go-to method they pushed. Thanks for pointing that out.
As for Docker Desktop being the top option, it would only be used for a “development environment” because why would you install that on a headless docker host for production? And after the horror stories I’ve heard of Windows and Mac versions of Docker Desktop, there isn’t a chance in hell I’d use it anyway.
So yes, going forward it looks like adding the repos and apt-get install are the way to go. Except, the convenience script was so… convenient.
Debian already has docker packaged. That’s more convenient.
With Debian not being a rolling release id think it is relevant to stay up to date with your container daemon. IMHO.
I’ve become very partial to Dozzle. I roll out right into my compose scripts and it’s incredibly lightweight.
I found dozzle a bit rudimentary as it only does logs, but I liked that there was an android app to interface it.
Lazydocker is more like Portainer on running stacks in that you can see logs, configs, stats and do operations on the stacks and components all from an SSH TUI.
I’ll have to check it out. TIL about the app.
Debian + Containers is definitely the way. Literally so stable it’s boring.
What is so bad about Ubuntu server?
When I tried it last (a couple years ago), the docker snap was an untroubleshootable mess. I don’t like the idea of running Docker that way, in whatever version of a container that Canonical has come up with for snaps. It’s just looking for problems. Run an application with Snap if you want, but a whole container system? No thanks.
I just don’t use snaps and it works great for me. For docker I add their apt repository and install it like that.
Well, I wasn’t using snaps and it still decided to install Docker snap on me. 2 days of troubleshooting before I figured out that the snap existed and was having a war with my apt install of docker. Never again.
I avoid apt because it does silly stuff. Always use apt-get. I suppose having to know that quirk is a con of the distro.
I wrote a script to remove snaps and install Docker as per the docker website. Works great mate.
Plus you get the benefit of frequent updates.
I don’t need what Ubuntu offers to run server applications, and Debian is rock solid and predictable. Might as well go to the source since it’s Debian all the way down anyway, just with added cruft.
One of their frequent updates completely broke docker on my system. Fortunately they did push the fix by the time I realized what happened.
Is that because you installed it via snaps instead of apt?
It was from docker’s apt repo, so a newer version than provided through Ubuntu’s channels I assume.