You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 25, 2020. It is now read-only.
Pulling the Docker image initially (and upon certain updates to the tag) requires downloading quite large layers (hundreds of megabytes). Have we considered using the Alpine Linux variant for the base image to reduce the size of layers? How difficult would it be to switch to that, and what tradeoffs would it involve?
Confession time: I put together the Docker image in the fastest way I possibly could. You're absolutely right it should be sitting on Alpine and be as small as possible (at which point also the wrapper script should pull before each run). I don't foresee any particular roadblocks with this (source: "Famous Last Words")
Confession time: I put together the Docker image in the fastest way I possibly could.
Fair enough, and good approach, I think. I know Adrian and I at least sometimes are running on not the fastest public internet, so the big pulls can be painfully slow. If I find time, I will try to convert things to Alpine, or some other more lightweight variant. I'm not sure when I will likely have time to do this, though, so if anyone else has time and interest, feel free to work on it.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Pulling the Docker image initially (and upon certain updates to the tag) requires downloading quite large layers (hundreds of megabytes). Have we considered using the Alpine Linux variant for the base image to reduce the size of layers? How difficult would it be to switch to that, and what tradeoffs would it involve?
/cc @abesto
The text was updated successfully, but these errors were encountered: