this post was submitted on 07 Nov 2024
14 points (85.0% liked)

Selfhosted

39982 readers
461 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
14
Help with docker setup (lemmy.ml)
submitted 19 hours ago by [email protected] to c/[email protected]
22 comments fedilink hide all child comments
 

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

top 22 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 8 hours ago* (last edited 7 hours ago) (2 children)

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.

[–] [email protected] 1 points 2 hours ago

What is so bad about Ubuntu server?

[–] [email protected] 3 points 8 hours ago

Debian + Containers is definitely the way. Literally so stable it's boring.

[–] [email protected] 6 points 19 hours ago (2 children)

Anything.

Personally I use Debian. But Docker doesn't care. I chose Debian because it is very stable and simple

[–] [email protected] 2 points 19 hours ago (1 children)

Yep, Debian and then add Portainer - for me this is the easiest setup to manage.

[–] [email protected] 3 points 18 hours ago (3 children)

would prefer to not use portainer

[–] [email protected] 1 points 1 hour ago

I love the one click pull from git option. Don't like the corporate direction they seem to be taking.

I haven't seen aby alternative docker GUI managers that have the git pull for the compose.

[–] [email protected] 2 points 8 hours ago

I can appreciate this. You might want to look at Lazydocker as a SSH TUI management tool.

[–] [email protected] 4 points 18 hours ago

I just said what works best for me. Use the command line and compose files if you want.

[–] [email protected] 1 points 19 hours ago (3 children)

And what is the good way of deploying it? After pulling the image, how do we autostart it etc...

[–] [email protected] 5 points 19 hours ago (1 children)

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.

[–] [email protected] 1 points 18 hours ago (1 children)

Should I make the docker compose files or pull the image from hub.docker.com?

[–] [email protected] 3 points 18 hours ago

Your compose file will pull the image when you run it, from the registry it's in

[–] [email protected] 3 points 19 hours ago (1 children)

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.

[–] [email protected] 1 points 18 hours ago* (last edited 18 hours ago) (1 children)

Are they starting automatically at boot?

EDIT : how do you run a container with a simple name instead of using his id?

[–] [email protected] 2 points 18 hours ago* (last edited 18 hours ago) (1 children)

Yes - they'll start automatically. There are other options for "restart" that define the behavior.

You can give whatever you like to "servicename" and use that rather than the ID.

For example:

docker run -d --name mysite --restart unless-stopped nginx

docker stop mysite

docker start mysite
[–] [email protected] 1 points 18 hours ago

thx

[–] [email protected] 1 points 19 hours ago

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.

[–] [email protected] 2 points 19 hours ago (1 children)

What do you want to do with containers? That’s sort of the driver for making architectural decisions.

[–] [email protected] 1 points 19 hours ago

Network and services containers. Nextcloud, Homepage, filesharing, ...

[–] [email protected] 1 points 18 hours ago (1 children)

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.

[–] [email protected] 1 points 18 hours ago

thank you a lot, im gonna dive in the subject more deeply