this post was submitted on 07 Nov 2024
24 points (85.3% liked)

Selfhosted

40474 readers
472 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 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
24
Help with docker setup (lemmy.ml)
submitted 3 weeks ago by foremanguy92_@lemmy.ml to c/selfhosted@lemmy.world
42 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

you are viewing a single comment's thread
view the rest of the comments
[–] foremanguy92_@lemmy.ml 1 points 3 weeks ago (4 children)

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

[–] lka1988@sh.itjust.works 5 points 3 weeks 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.

[–] foremanguy92_@lemmy.ml 1 points 3 weeks ago (1 children)

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

[–] mhzawadi@lemmy.horwood.cloud 4 points 3 weeks ago

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

[–] atzanteol@sh.itjust.works 3 points 3 weeks 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.

[–] foremanguy92_@lemmy.ml 1 points 3 weeks ago* (last edited 3 weeks 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?

[–] atzanteol@sh.itjust.works 2 points 3 weeks ago* (last edited 3 weeks 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
[–] ryan_harg@discuss.tchncs.de 3 points 3 weeks ago

in a docker compose file you can set the option "restart: unless-stopped"

https://docs.docker.com/reference/compose-file/services/#restart

[–] Itwasthegoat@lemmy.world 1 points 3 weeks 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.