2021-04-11 19:53:44 UTC - Matt Welke: I noticed the action Docker image for Go wasn't based on Alpine or a similar distro optimized for size for running things in production. I looked at the image size and noticed it was pretty big too (looked at Go 1.15 in particular).
I noticed after pulling some Node.js images too that they also are quite large. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1618170824116000 ---- 2021-04-11 19:54:12 UTC - Matt Welke: Is this because of OpenWhisk needing the build toolchain of each runtime in order to compile the code as the container that will serve requests starts up? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1618170852116600 ---- 2021-04-11 19:54:36 UTC - Matt Welke: (And with runtimes like Node.js, needs the toolchain to run the code) https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1618170876117200 ---- 2021-04-11 19:55:39 UTC - Matt Welke: Also I'm wondering if the large image sizes have ever been a problem. I thought it'd be neat to optimize them by trying a smaller base image (like Alpine or a "slim" variant), but maybe there's optimizations done like pre-fetching all action runtime images on a new node, that way the images are always ready to go and it's not a problem if they're large. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1618170939118500?thread_ts=1618170939.118500&cid=C3TPCAQG1 ----
