Hacker News Reader

Comment by globular-toast | Hacker News Reader

Curious why people feel the need for tools like this. I think git benefits massively from a graphical tool but I don't really see the point for docker, docker compose or even kubernetes. I do find CLI completions essential, though.

View on HN

Docker benefits from a graphical tool for the same reason as git does; both CLI tools often require using long id strings from the output of one command as the input of another command.

CLI is good and the best way to manage docker containers, however editing that compose file from a browser tab and hitting recreate slaps different. A web GUI makes it so that users who are otherwise intimidated by CLI can still make use of docker.

I would be worried about where that compose file is being stored. I keep my compose files in a git repo and after I edit them just do `docker compose up -d` (in fact, I hit a key in my editor and it runs that for me, showing the output).

Those are 2 hops as opposed to editing and applying the changes from a single interface. With git, assuming you are talking about an online repo, there is always the worry of accidentally leaking credentials etc. Though I assume the project mentioned here is all local so the compose files will be saved in a local directory.

I suppose the two methods (CLI and GUI) don't make much difference but they appeal to different users, maybe even different occasions for the power user.

Check out k9s, if you use kubernetes. It made me 100x more efficient when working across multiple clusters and namespaces.

I haven't tried it yet, but if it cuts a step in my development process then yes please!

Reply on news.ycombinator.com