Selfhosted

39435 readers

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

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.
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.
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).
No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

124

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

submitted 1 year ago by [email protected] to c/[email protected]

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

[–] [email protected] 1 points 1 year ago (2 children)

I'm actually doing both right now since I had quite a huge compose file that I haven't converted to ansible yet. The biggest frustration I have is that there doesn't seem to be an ansible module that works with compose v2 (the official plugin) which means I'm either stuck on the old version of compose or I have to use shell commands to run stuff like 'docker compose up -d'.

One nice thing I've gained though is for services like Plex. I have an 'update' playbook that I use and it will check to see if Plex is actively streaming before updating the container which isn't something I could do easily with compose.

[–] xcjs 1 points 1 year ago

I'm still using the old docker-compose executable - my Docker role is still installing it until the Ansible module catches up.

[–] [email protected] 1 points 1 year ago

Well the v2 plugin is basically a binary, while v1 is written with Python, which makes it super easy to write an Ansible module