kocolosk commented on a change in pull request #90:
URL: https://github.com/apache/couchdb-pkg/pull/90#discussion_r800837706
##########
File path: build.sh
##########
@@ -31,10 +31,10 @@ SCRIPTPATH="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd
)"
DEBIANS="debian-stretch debian-buster debian-bullseye"
UBUNTUS="ubuntu-bionic ubuntu-focal"
CENTOSES="centos-7 centos-8"
-XPLAT_BASE="debian-buster"
-XPLAT_ARCHES="arm64v8 ppc64le"
+XPLAT_BASE="debian-bullseye"
+XPLAT_ARCHES="arm64 ppc64le"
Review comment:
This StackOverflow answer provides some extra detail:
https://stackoverflow.com/a/70889505/4797770
It looks like `containerd` will happily normalize `arm64/v8` as `arm64`, but
`arm64v8` is treated as a separate architecture entirely.
I also found that while we would use `arm64v8` in the name of the
single-arch images that we had been publishing, the architecture was actually
labeled as `arm64`.
Bottom line: because we are identifying the image to use via the
`--platform` flag instead of the prefix in the single-arch image name, we need
to use `arm64` or `arm64/v8` and not `arm64v8` here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
