mmh0000
7 hours ago
I am so not understanding the purpose of this...
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…fragmede
4 hours ago
Are you on a desert island with no access to the Internet? If you don't know docker, what's faster? Reading all of the documentation first and then figuring out the difference between, say, run and exec, or just copy and pasting a command from a tutorial until it sinks in and you gain a better understanding? This is the AI information age. If docker has eaten your hard drive, and again, you don't know docker, is it easier to have ChatGPT tell you, or muddle around with ps, rm, images, rmi and all of the various options.
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.
rendaw
2 hours ago
How do you know which command to copy and paste? Unless you're suggesting to just try them randomly until you get one that seems to do what you want.
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.