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 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: [email protected]
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.
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).
That is one
docker compose up -dfor each file you copied over, right… Or are you doing something even smarter?I have one docker-compose.yml for each service. You can use
docker compose -f /path/to/docker-compose.yml up -din scriptsI would never use “one big” file for all. You only get various problems imo
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.
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
I have all services in one compose file. Up -d starts them all. Servicename up -d is more selective.