...
$ docker load < e3sm_2021.03.1819.tar
Example
By default, Docker containers do not use the host filesystem. Any host system directories that, a user wants to make accessible from the container environment, must be mounted when the container is started. A directory with SSH private keys will be needed in the container, if you plan to ssh from the container (clone the E3SM repository recursively). If you have the E3SM repository already cloned on your host system, and you want to work on it in the container environment, you need to mount it as well. Also do mkdir -p $HOME/projects/e3sm/cesm-inputdata (this directory is assumed to exist by the machine entry above. Input data will be downloaded here. (could get large, THE CONTAINER DOES NOT HAVE INPUT DATA)).
...
--shm-size=512m \
e3sm:2021.03.18 19 /bin/su - e3sm
The command starts a Docker container with e3sm:2021.03.18 19 image, mounts your .ssh/ directory to a corresponding directory of the ‘e3sm’ user in the container, mounts your e3sm project data directory projects/e3sm to a corresponding directory in the container, and run a command to switch to the ‘e3sm’ user in the container. By default, Docker sets a memory usage limit for containers on macOS and Windows systems to 2 GB. The limit may trigger the OOM Killer that will kill a running case with 9 signal. If needed, a memory limit can be increased with the -m option when starting a docker container, e.g. -m 16g.
...