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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Ubuntu server is pretty user friendly and has more frequent updates op. Plenty of info out there. My preference is uninstall snaps.
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.
Anything.
Personally I use Debian. But Docker doesn’t care. I chose Debian because it is very stable and simple
And what is the good way of deploying it? After pulling the image, how do we autostart it etc…
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.
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, …