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
I just added alpine-3.18 as a base image (frolvlad/alpine-glibc:alpine-3.18 to be exact). I failed to notice that I had not configured image tagging that will allow us to have more than one alpine image per micromamba version (ie, we have alpine, not alpine3.17 and alpine3.18). I will look into supporting multiple alpine images.
Currently for our non-alpine images, there is a distribution release identifier tag (we have a bookworm tag, not a debian tag). But we don't have this for alpine. Should we deprecate the alpine tag and move to alpine3.18? That would seem to be the most consistent and it allows me to add newly released base images (ie, alpine3.19) without having to wait for a minor version release of micromamba (so that we don't end up with what I accidentally did today, where a tag alpine can change from one distro release to another). The other option would be to:
keep alpine as a tag
add alpine3.17 and alpine3.18 as tags
add release independent distro tags for debian, ubuntu, and ubuntu-cuda
and then only add base images on a minor version release of micromamba
I'm inclined to go with the former option (deprecate alpine).
The text was updated successfully, but these errors were encountered:
I just added
alpine-3.18
as a base image (frolvlad/alpine-glibc:alpine-3.18
to be exact). I failed to notice that I had not configured image tagging that will allow us to have more than one alpine image per micromamba version (ie, we havealpine
, notalpine3.17
andalpine3.18
). I will look into supporting multiple alpine images.Currently for our non-alpine images, there is a distribution release identifier tag (we have a
bookworm
tag, not adebian
tag). But we don't have this foralpine
. Should we deprecate thealpine
tag and move toalpine3.18
? That would seem to be the most consistent and it allows me to add newly released base images (ie,alpine3.19
) without having to wait for a minor version release ofmicromamba
(so that we don't end up with what I accidentally did today, where a tagalpine
can change from one distro release to another). The other option would be to:alpine
as a tagalpine3.17
andalpine3.18
as tagsdebian
,ubuntu
, andubuntu-cuda
micromamba
I'm inclined to go with the former option (deprecate
alpine
).The text was updated successfully, but these errors were encountered: