Closed weiji14 closed 1 day ago
I haven't tested this, but you can merge this in @scottyhq and tag a new version to see if it works.
This didn't quite work... But fortunately it's okay to break things ;)
I think this is what we need to do: https://github.com/docker/buildx/issues/1744#issuecomment-1896645786
# TAG -> master -> date / latest
docker buildx imagetools create pangeo/base-image:master -t pangeo/base-image:latest -t pangeo/base-image:2024.07.02
docker buildx imagetools create quay.io/pangeo/base-image:master -t quay.io/pangeo/base-image:latest -t quay.io/pangeo/base-image:2024.07.02
This also looks useful! https://github.com/regclient/regclient
:rocket: Fixed for images>2024.07.02 https://github.com/pangeo-data/pangeo-docker-images/actions/runs/9767498538
Ah nice, that docker buildx
method looks much cleaner, less lines of code to deal with! Which reminds me, maybe we should revisit buildx a bit more, xref #357.
The
base-image
,base-notebook
andpangeo-notebook
Docker images only had linux/amd64 platform available on the latest and CalVer tags (see e.g.pangeo-notebook:2024.06.28
), whereas the master tag has bothlinux/amd64
andlinux/arm64
:Need to use the
--platform
flag when doingdocker pull
ordocker push
, so that the linux/arm64 images will be made available forlatest
and Calver tags.Patches #399