Use Multi-Arch Build instead of creating separate images

[Moulberry]

Currently, there exists both community (amd64) and community-aarch64 (arm64) packages.

This is undesirable for multiple reasons:

• It makes it difficult for developers to find the correct images (not helped by Docker Hub's searching)
• It complicates the set-up when using docker compose (and presumably swarm, k8s, etc.), because now two separate docker-compose.ymls need to be created, one specifying community and the other community-aarch64
• It complicates documentation because different example commands need to be used for different architectures.

The preferred method for supporting multiple architectures is to create a single "multi-architecture" image, as outlined here https://docs.docker.com/desktop/multi-arch/
Doing so will allow referencing the single tag community, and the appropriate image for the current architecture will be fetched automatically

I acknowledge that a multi-arch image might not be so simple to build. In any case, thank you for your consideration.

[ceejatec]

It is in fact on the roadmap, hopefully for our next release. I'll add a link here from our internal tracking ticket so I remember to update the status here.

I'm not sure if there will be a community build for the next release, but it not, once we have the infrastructure in place I will seek internal permission to re-publish 7.1.0-community as a multi-arch image.

[ceejatec]

couchbase/server:7.1.1-community was released recently, supporting both amd64 and arm64v8 architectures.