The Overhead of Docker Run
Travis Reeder

Note that the results might depend on the filesystem driver you use for docker. I typically see an overhead of about 260ms using overlayfs for creating a fresh container (on Linux with a 4.4 kernel )

You reuse the stop container (confused me at first). I thought you would spin up the container and then use exec to run the shell script.

When I do that I get:
 Hello World!

real 0m0.044s
user 0m0.006s
sys 0m0.004s

that should be the overhead of the docker daemon. I’m still puzzled this is really 44ms.
Talking to a local docker-daemon and streaming the result back should not take 44ms …

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.