Selfhosted

39435 readers

5 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 1 year 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] 7 points 1 year ago (2 children)

Ive almost completely moved to podman managed by systemd and I highly recommend it.

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

I do this out of habit because this is how my work does it, but I honestly don't know the benefits of doing it this way. Can you explain (or provide a link?)

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

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/building_running_and_managing_containers/assembly_porting-containers-to-systemd-using-podman_building-running-and-managing-containers

Ive found it to just be easier to manage rootless containers this way.

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

I've never tried Podman myself, but managing the containers using systemd would mean that you use exactly the same commands to start a Docker container as you would use to start a regular service. The fact that it's running in a container essentially just becomes an implementation detail, and you don't have to remember what's running in containers vs what's not running in containers.

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

Do you use podman run followed by podman generate or are you using quadlet?

Quadlet is integrated in podman 4.4 and up and makes it possible to declare your containers in .container files that look like systems unit files and still get the full systems integration: https://www.redhat.com/sysadmin/multi-container-application-podman-quadlet

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

I just generate them. Never heard of quadlet I'm gonna check it out, thanks.