It appears that an experimental containerd image store feature on Apple Silicon hardware breaks Deephaven builds with an error that looks something like "Could not build image: failed to export image: no match for platform in manifest".
This appears to only be triggered through the usage of the Docker remote API (which our build uses via the gradle-docker-plugin), as I was able to do a short test on some hardware which demonstrated that docker build --platform=linux/amd64 ... and docker buildx build --platform=linux/amd64 --load ... seemed to work.
This was originally reported by a community user on a new M3. It may be possible to explicitly enable the containerd image store on M1 to reproduce this issue.
It appears that an experimental containerd image store feature on Apple Silicon hardware breaks Deephaven builds with an error that looks something like "Could not build image: failed to export image: no match for platform in manifest".
This appears to only be triggered through the usage of the Docker remote API (which our build uses via the gradle-docker-plugin), as I was able to do a short test on some hardware which demonstrated that
docker build --platform=linux/amd64 ...anddocker buildx build --platform=linux/amd64 --load ...seemed to work.I originally suspected the containerd image store after seeing a similar looking issue posted https://github.com/moby/buildkit/issues/3891.
This was originally reported by a community user on a new M3. It may be possible to explicitly enable the containerd image store on M1 to reproduce this issue.