Docker image or install is not working for M3 Macs

[ericepalmer]

ISIS version(s) affected: x.y.z

Description
Trying to install ISIS on a M3 mac using Docker. I downloaded the listed Docker image from DockerHub, but that is a AMD64 archecture rather than the new Apple silicon. I followed the instructions to build the docker image, which fails.

How to reproduce
I downloaded the production.dockerfile and ran the listed command, "docker build -t isis -f production.dockerfile .". It gives the following error: (note, some steps have been cached from the previous attempts)

epalmer@danzig Downloads % docker build -t isis -f production.dockerfile . [+] Building 9232.8s (7/9) docker:desktop-linux => [internal] load build definition from production.dockerfile 0.0s => => transferring dockerfile: 461B 0.0s => [internal] load metadata for docker.io/usgsastro/miniconda3:latest 0.9s => [auth] usgsastro/miniconda3:pull token for registry-1.docker.io 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [1/5] FROM docker.io/usgsastro/miniconda3:latest@sha256:0dc2c8fe65339bc97055e482d91e8047b43ef4d75af 0.0s => CACHED [2/5] RUN conda update conda && conda install python=3.6 && conda config --add chann 0.0s => ERROR [3/5] RUN conda install -c usgs-astrogeology isis 9231.8s

---

[3/5] RUN conda install -c usgs-astrogeology isis:
2.910 Collecting package metadata (current_repodata.json): ...working... done
153.2 Solving environment: ...working... failed with initial frozen solve. Retrying with flexible solve.
817.4 Solving environment: ...working... failed with repodata from current_repodata.json, will retry with next repodata source.
1700.0 Collecting package metadata (repodata.json): ...working... done 2299.2 Solving environment: ...working... Killed

production.dockerfile:10

8 | conda config --add channels usgs-astrogeology 9 |
10 | >>> RUN conda install -c usgs-astrogeology isis 11 |
12 | RUN apt-get update && \

ERROR: failed to solve: process "/bin/sh -c conda install -c usgs-astrogeology isis" did not complete successfully: exit code: 137

Possible Solution
Suggest building and hosting a M1/M2/M3 chip on DockerHub and/or fix the error 137.

[jlaura]

Thanks for the issue:

• Issue #4753 is already open and tracking the desire for ARM builds.
• Exit Code 137 is thrown by docker. Generally, when the container has insufficient RAM.
• There are currently no maintainers on this project packaging docker containers and hosting them on either DockerHub or a non-commercial alternative container registry. Anyone should feel empowered to fill that role should they have the time available to dedicate to the effort. From what I have seen, the maintainers (I am no longer one) on this project are quite busy and do not have the bandwidth to adopt additional responsibilities.
• The original post is quite hard to read. Please consider checking out the GitHub Markdown docs that describe formatting code.