6 ms·
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.
by lazide 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.
- 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.