132

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
[-] giacomo@lemmy.world 1 points 3 years ago

I'm sure someone has written a script to convert docker run commands to compose files.

I am usually customizing variables and tend to use compose for anything I am planning on running in "production". I'll use run if it's a temporary or on-demand use container.

It's not really that much effort to write a compose file with the variables from a run command, but you do have to keep an eye on formatting.

[-] ghulican@lemmy.ml 7 points 3 years ago

composerize.com

It’s saved me countless minutes.

[-] giacomo@lemmy.world 1 points 3 years ago

Nice! Yeah, literally minutes, haha. I knew someone had to have already done this.

[-] Zephyr@feddit.nl 2 points 3 years ago

use chatgpt for that... It can also create your ansible task...

[-] giacomo@lemmy.world 1 points 3 years ago

Great... For chatgpt...

this post was submitted on 12 Jul 2023
132 points (100.0% liked)

Selfhosted

61126 readers
456 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

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. 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, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS