I must be getting old.
If you need Docker CLI commands, isn't it just easier to use the CLI that you're already on?
Docker is fully self-documented:
/ # docker
Usage: docker [OPTIONS] COMMAND
A self-sufficient runtime for containers
Common Commands:
run Create and run a new container from an image
exec Execute a command in a running container
…SNIP…
/ # docker run --help
Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
Create and run a new container from an image
Aliases:
docker container run, docker run
Options:
--add-host list Add a custom host-to-IP mapping (host:IP)
…SNIP…If you have a command with a bunch of flags, static documentation like man pages are just such a poor interface compared to eg explainshell.com. This opinion obviously gets me thrown out of the Unix grey beards club, but I don't have a beard and it's not grey.
There are plenty of commands where the documentation is nearly impenetrable (e.g. ffmpeg, or if it exists at all), but I think GP's point was that for docker it's fairly simple.
IMO except for the concrete examples for docker run/exec, this website looks more or less exactly like the CLI help output for docker.
What a terrible question. Why do you think speed is a good metric? Why is it better to copy-paste in 2 seconds than to read the manual for 20 minutes and learn the basics? What would have happened?
Because time is the great equalizer. Everyone only gets 86400 seconds in the day. How you spend them is up to you.
There are some things with a very steep learning curve, like vim, that one decides for themselves if it's worth investing their time in to learn. Or not. Most things have a shallower learning curve though, thankfully. The first time you interact with Docker, how do you know you're ever going to use it again? How do you know you're going to reap rewards of those 20 minutes. How do you know which of the dozen random tool you come across on a stroll of the Internet is worth investing the 20 minutes? Apriori, you can't.
So you copy and paste in 2 seconds, and if it turns out that you use that tool more than once, then go take those 20 minutes and learn how to use it right and use it well. What's the opportunity cost of those 28 minutes? What other piece of technology could this user have been learning? Is there something more appropriate for their particular role? Maybe it's something that's not even computer related that's important for their life.
It is important to remember that while this is true time is not the ONLY criteria.
The goal is basically to package the same info in a nicer, modern UI that’s more pleasant to use than terminal help output. I’ll also add more things like "Recipes". This was just the first version.
But you’re always free to use whatever you prefer.
EDIT: Actually the biggest might be that containers often need a fully qualified name, so instead of `run name/container:latest` you need `run docker.io/name/container:latest`. You can configure default search domains though.
The biggest thing people will (did?) miss is docker-compose. There was a third party `podman-compose` but now it seems that's actually been folded under the official umbrella, along with a `podman compose` command that will "Run compose workloads via an external provider such as docker-compose or podman-compose" so even that gap might be closed up now. Honestly I swapped to just scripting it myself when I swapped to podman - before even the third party podman compose existed, either using sh, .kube files or now systemd units. If you're used to using big 5-10+ container compose files you might have some friction there, might not.
There are differences internally, ex: docker primarily runs as root and has a different networking stack compared to podman, but for most usage on a dev machine it doesn't matter, and matters maybe in a deployment, maybe not.
Unsolicited opinion, I originally found Podman much less intrusive, dockers iptable muckery always rubbed me the wrong way, so it defaulting to userspace and just letting me do any nftable routing I wanted felt much nicer. It also just fees less icky when using it where its default or configuration options were less funnel-you-into-docker.com.
anagogistis•2w ago
crtasm•2w ago
anagogistis•2w ago
crtasm•2w ago
yogirk1•2w ago
tomhow•2w ago
https://news.ycombinator.com/showhn.html