4 ms·
> I see a use case. The other day I wished that I could pack CLI commands as docker containers and execute them as CLI commands and get return codes I don't un
by lelanthran 2y ago
> I see a use case. The other day I wished that I could pack CLI commands as docker containers and execute them as CLI commands and get return codes
I don't understand this requirement/specification; presumably this use-case will not be satisfied by a shell script, but I don't see how.
What are you wanting from this use-case that can't be done with a shell script?
- lazide 2y agoPresumably, they don’t want to write/maintain a shell script wrapper for every time they want to do this, when they could use a tool which does it for them.
- lelanthran 2y ago> Presumably, they don’t want to write/maintain a shell script wrapper for every time they want to do this, when they could use a tool which does it for them. How's "packing" cli commands into a shell script any different from "packing" CLI commands into a container?
- lazide 2y agoCalling a container on the CLI is a pain in the ass. People generally don’t put stuff that works in whatever environment you’re in on the CLI already into contains. Stuff that doesn’t, of course they do. Having a convenient shell script wrapper to make that not a pain in the ass, while letting all the environment management stuff still work correctly in a container is convenient. Writing said wrapper each time, however is a pain in the ass. Generating one, makes it not such a pain in the ass to use. So then you get convenient CLI usage of something that needs a container to not be a pain in the ass to install/use.
- james_marks 2y agoAn icon a non-technical user can click to run it.
- cmeacham98 2y agoA non-technical user that has docker installed?