Selfhosted @lemmy.world foremanguy @lemmy.ml 1w ago

Help with docker setup

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

42 comments

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.

Avoid bare docker run commands. It makes an unmanageable mess when you get more that a couple containers running.

Consider using the nextcloud AIO master container. It runs docker containers inside a master container compose file, and it is by far the easiest way to manage and run nextcloud.
- 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.
- Debian with the docker convenience script.
  
  They seem to be moving away from this, and it's not longer the first option on their install page
  
  On their debian page
  
  Use a convenience script. Only recommended for testing and development environments
  
  Also, it should be noted about the first option they recommend, Docker Desktop, that Docker Desktop is proprietary.
  
  I recommend just getting the docker.io and docker-compose from 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 + 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.
Anything.

Personally I use Debian. But Docker doesn't care. I chose Debian because it is very stable and simple
- Yep, Debian and then add Portainer - for me this is the easiest setup to manage.
  
  would prefer to not use portainer
- And what is the good way of deploying it? After pulling the image, how do we autostart it etc...
  
  The Docker documentation is pretty terrible, but it's a decent start. Start by looking at docker-compose.yml files for the services you want to run and the write-ups for those.
  
  Something nobody ever told me, that I had to figure out myself, is that docker-compose.yml files can be placed anywhere you want.
  
  At its simplest:
  
  docker run -d --name servicename --restart unless-stopped container
  
  That'll get you going. Youi'll have containers running, they restart, etc. There are more sophisticated ways of doing things (create a systemd file that starts/stops the container, use kubernetes, etc.) but if you're just starting this will likely work fine.
  
  in a docker compose file you can set the option "restart: unless-stopped"
  
  https://docs.docker.com/reference/compose-file/services/#restart
  
  Create a systemctl service for it, create a cron, or of there is a lot of interconnectivity between your containers look at something like K3S.
I would start with a Debian os base, install docker and turn it into a swarm manager. Then look at stacks and how services work, if you find your running your host too hard. You can add a work host and stread out.

Once you have docker swarm running, get portainer running. I use portainer as a visual whats happening on my swarm, but I use the docker cli to start and update all my stacks. I have my stacks in a git repository so that I have a backup and history of what changes I did.

Now your a docker master, of sorts.
- thank you a lot, im gonna dive in the subject more deeply
What do you want to do with containers? That’s sort of the driver for making architectural decisions.
- Network and services containers. Nextcloud, Homepage, filesharing, ...
Ubuntu server is pretty user friendly and has more frequent updates op. Plenty of info out there. My preference is uninstall snaps.

42 comments