REQUEST: arm64 archive not just aarch64

[SamuelMarks]

Please provide a small Dockerfile that demonstrates your issue.

There's a special TARGETARCH I can use so I can avoid explicitly doing --build-arg ARCH=$(uname -m):

FROM ubuntu
ARG S6_OVERLAY_VERSION='3.2.0.3'
ARG TARGETARCH
RUN apt-get update && apt-get install -y nginx xz-utils && \
    echo "daemon off;" >> /etc/nginx/nginx.conf
CMD ["/usr/sbin/nginx"]

ADD https://github.com/just-containers/s6-overlay/releases/download/v"${S6_OVERLAY_VERSION}"/s6-overlay-noarch.tar.xz /tmp
RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz
ADD https://github.com/just-containers/s6-overlay/releases/download/v"${S6_OVERLAY_VERSION}"/s6-overlay-"${TARGETARCH}".tar.xz /tmp
RUN tar -C / -Jxpf /tmp/s6-overlay-"${TARGETARCH}".tar.xz
ENTRYPOINT ["/init"]

TARGETARCH normalises as both aarch64 and arm64 are the same, see: https://github.com/BretFisher/multi-platform-docker-build/blob/main/README.md#the-problem-with-downloading-binaries-in-dockerfiles

To avoid breaking anyones scripts can you just copy s6-overlay-aarch64.tar.xz & its checksum to s6-overlay-arm64.tar.xz and release it on GitHub Releases?

Thanks

EDIT: This issue will be closed by #561

[skarnet]

The comments I made under #561 are still accurate. Do you have a solution for these?

[SamuelMarks]

@skarnet Yeah basically a big case something like:

case "${ARCH}" in
  'aarch64')  export ARCH='arm64' ;;     # the latest v8 arm architecture. Used on Apple M1, AWS Graviton, and Raspberry Pi 3's and 4's
  'armhf') export ARCH='arm' ;;       # 32-bit v7 architecture. Used in Raspberry Pi 3 and  Pi 4 when 32bit Raspbian Linux is used
  'armel')  export ARCH='arm/v6' ;;    # 32-bit v6 architecture. Used in Raspberry Pi 1, 2, and Zero
#   i386     386        # older Intel 32-Bit architecture, originally used in the 386 processor
  'i386') export ARCH='386'  ;;
#   x86_64   amd64      # all modern Intel-compatible x84 64-Bit architectures
#   x86-64   amd64
  'x86_64'|'x86-64') export ARCH='amd64' ;;
esac

Then just release duplicate archives on GitHub releases so as not to break any existing workflow of your userbase.

[skarnet]

Yes, your solution is to release duplicates. This is precisely what I would like to avoid.

[SamuelMarks]

I don't think there's any way to avoid duplicates. I understand your wish for GitHub to have symbolic links… but alas they don't have this feature.

Without this solution you have to use RUN and lose the cache—and lightweight curl/wget free base image—advantage of ADD.