125
Anyone using "docker run" instead of "docker compose"? (feddit.it)
submitted 1 year 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
[-] jalim@jalim.xyz 2 points 1 year ago

Something that always confused me was how docker doesn’t come with compose installed as a core component.

[-] radiated@lemm.ee 2 points 1 year ago

docker compose vs docker-compose. Yes I know it’s stupid.

[-] jalim@jalim.xyz 2 points 1 year ago

Well today I learned something! I’ve been using docker-compose for 5+ years now and I never happened upon the addition of compose to docker haha.

It’s also the issue with the internet and all the fantastic guides which even if they were written 12 months ago, are already out of date!

this post was submitted on 12 Jul 2023
125 points (93.1% liked)

Selfhosted

39677 readers
364 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz