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
With alpine, we might have to ditch the machinery we currently have that creates a parigot user and then makes all the tools and such owned by the parigot user and group. It's ok if this goes away to get us to a much smaller container size.
There is are already some tags that provide access to an alpine-based container image with golang.
Currently, the dev container is 4.6GB because it includes an ubuntu server and a ton of added packages.
Shrink the size of the devcontainer using multi-stage builds
With alpine, we might have to ditch the machinery we currently have that creates a
parigot
user and then makes all the tools and such owned by the parigot user and group. It's ok if this goes away to get us to a much smaller container size.There is are already some tags that provide access to an alpine-based container image with golang.
1.19.4-alpine3.17, 1.19-alpine3.17, 1-alpine3.17, alpine3.17, 1.19.4-alpine, 1.19-alpine, 1-alpine, alpine
The text was updated successfully, but these errors were encountered: