4 ms·
> or you need to run it as a container (which may or may not have significant overhead depending on how it was built) What overhead are you referring to? It ru
by moondev 4y ago
> or you need to run it as a container (which may or may not have significant overhead depending on how it was built)
What overhead are you referring to? It runs, prints the cmdline and exits.
- codazoda 4y agoI’m talking about the base image overhead. Honestly, I hadn't tried it on this tool. As an example, if the container was using Ubuntu as a base, you might fetch a big base image. If it’s using scratch, no problem. So, it depends on how it’s built and I didn’t dig in. Edit: I’ve gone back and looked at the dockerfile. The base image is Ubuntu, so the docker image is heavy. I fetched the indicated image from Dockerhub and it's 228.13 MB. Most of the command line tools in my toolbox are measured in K not in hundreds of MB.