this post was submitted on 12 Jul 2023
116 points (92.6% liked)

Selfhosted

40355 readers
342 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
 

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"...

(page 2) 20 comments
sorted by: hot top controversial new old
[–] giacomo@lemmy.world 1 points 1 year ago (3 children)

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.

[–] Zephyr@feddit.nl 1 points 1 year ago (1 children)

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

[–] giacomo@lemmy.world 0 points 1 year ago

Great... For chatgpt...

load more comments (2 replies)

I really wish more projects did things like this.

I like just running docker compose and manage containers that way instead of remembering what flags I need to include.

[–] RedShadowWizard@sh.itjust.works -1 points 1 year ago (1 children)

Virgin docker compose. Chad Kubectl apply.

[–] antsu@geddit.social 1 points 1 year ago

Kubernetes is just docker-compose with extra steps.

/s

load more comments
view more: ‹ prev next ›