Multi-architecture miniforge docker container

[westurner]

Could this include the arch string in the miniforge download URL?

docker-images/miniforge3/Dockerfile

Line 25 in 8ae623a

RUN wget --no-hsts --quiet https://github.com/conda-forge/miniforge/releases/download/${MINIFORGE_VERSION}/Miniforge3-${MINIFORGE_VERSION}-Linux-x86_64.sh -O /tmp/miniforge.sh && \

https://github.com/conda-forge/miniforge/releases

• Miniforge3-${MINIFORGE_VERSION}-Linux-x86_64.sh
• Miniforge3-${MINIFORGE_VERSION}-Linux-aarch64.sh
• Miniforge3-${MINIFORGE_VERSION}-Linux-ppe64le.sh

How to make the Dockerfile pass the arch through to be templated into the miniforge release URL?

• In docker experimental mode, the --platform flag works
  • it sets DEB_TARGET_GNU_CPU=aarch64
• In lieu of waiting for things to emerge from experimental mode in the moby project, specifying the CPU arch as a build ARG or ENV variable (TARGET_CPU_ARCH=x86_64 | aarch64 | ppe64le may be the most portable way to support multiple architectures (and any container builder) with the miniforge docker container.

...

• If multi-OS is also a goal, the ansible molecule dockerfile shows one way to execute different package commands depending upon the existence of various package managers:
  https://github.com/ansible-community/molecule/blob/master/molecule/data/Dockerfile.j2#L17-L22

[westurner]

Whoops. Closing as a duplicate of #102; which isn't specifically about miniforge but is still pretty much the same issue.