Selfhosted

60543 readers

1060 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

125

Anyone using "docker run" instead of "docker compose"? (feddit.it)

submitted 3 years ago by Moonrise2473@feddit.it to c/selfhosted@lemmy.world

72 comments fedilink hide all child comments

For the vast majority of docker images, the documentation only mention a super long and hard to understand "docker run" one liner.

Why nobody is placing an example docker-compose.yml in their documentation? It's so tidy and easy to understand, also much easier to run in the future, just set and forget.

If every image had an yml to just copy, I could get it running in a few seconds, instead I have to decode the line to become an yml

I want to know if it's just me that I'm out of touch and should use "docker run" or it's just that an "one liner" looks much tidier in the docs. Like to say "hey just copy and paste this line to run the container. You don't understand what it does? Who cares"

The worst are the ones that are piping directly from curl to "sudo bash"...

you are viewing a single comment's thread
view the rest of the comments

[–] casrou@feddit.dk 2 points 3 years ago (2 children)

That is one docker compose up -d for each file you copied over, right.. Or are you doing something even smarter?

[–] morethanevil@lmy.mymte.de 3 points 3 years ago (1 children)

I have one docker-compose.yml for each service. You can use docker compose -f /path/to/docker-compose.yml up -d in scripts

I would never use "one big" file for all. You only get various problems imo

[–] SheeEttin@lemmy.world 3 points 3 years ago (1 children)

You use a separate file for each service? Why? I use one file for each stack, and if anything, breaking them out would give me issues.

[–] morethanevil@lmy.mymte.de 2 points 3 years ago

I meant stack 😸

My structure is like

/docker/immich/docker-compose /docker/synapse/docker...

But I read that some people make one big file for everything

[–] prenatal_confusion@lemmy.one 2 points 3 years ago

I have all services in one compose file. Up -d starts them all. Servicename up -d is more selective.