1. The user works interactively inside the container. The external experiment directory is mounted as a sub-directory inside the container environment. Depending on the configuration the user can either have access to the entire OpenIFS installation inside the container or the user may be prevented from accessing the source code. 
    
2. The user only works from the experiment directory, instead of executing the model binary program the OpenIFS run script starts up a container environment wherein the experiment runs in isolation. Immediately after the experiment has completed the container is removed. The user has no access to any part of the model installation. 

Dockerfile.oifs<RELEASE>.<NOTE>.<ARCH>.<TYPE>

RELEASE:   The OpenIFS release , e.g. 43r3v1.

NOTE:         Describes features of this build, in our examples this is either 'user' or 'root'.

ARCH:         The architecture for which this image is built, e.g. x86_64.

TYPE:          Type of build. Here 'bld' is used but could be changed to 'dev' or 'test' for example. 

% cd tools/docker

% ls Dockerfile*
Dockerfile.oifs43r3v1.root.x86_64.bld	Dockerfile.oifs43r3v1.user.x86_64.bld

% cp Dockerfile.oifs43r3v1.user.x86_64.bld  Dockerfile

Make sure the version number of the tarfile matches that specified in the Dockerfile, the build process will unpack this file inside the container.

-rw-r--r-- 1 glenn staff 4255 6 May 17:35 Dockerfile
-rw-r--r-- 1 glenn staff 30611901 6 May 18:13 oifs43r3v1.tar.gz

% docker build -t oifs43r3v1.user   .         #  note the trailing '.' to build in the current dir

For the docker image on the workstations at ECMWF four variables need to be set for network proxies in order to access the internet from within the container.

docker build -t oifs43r3v1.user --build-arg http_proxy="$http_proxy" --build-arg ftp_proxy="$ftp_proxy" --build-arg https_proxy="$https_proxy" --build-arg no_proxy="$no_proxy"  .

% docker images
REPOSITORY             TAG                 IMAGE ID            CREATED             SIZE
oifs43r3v1.user        latest              982f6e82bb93        39 minutes ago      873MB
ubuntu                 latest              72300a873c2c        13 days ago         64.2MB

% docker run -it oifs43r3v1.user
oifs@40a923f11202:~$

oifs@40a923f11202:~$ ls
oifs43r3v1
oifs@40a923f11202:~$ ls oifs43r3v1
CHANGES  COPYING  NOTICE  READMEs  examples  make                   oifs-config.sh  t21test       tools
CITE     LICENSE  README  bin      fcm       oifs-config.editme.sh  src             t21test_xios
oifs@40a923f11202:~$ 

oifs@40a923f11202:~$ ls oifs43r3v1/make/gnu-opt/oifs/bin
getres.exe  grib_set_vtable.exe  master.exe  spinterp.exe  timeint.exe  vod2uv.exe
gptosp.exe  intsst.exe           rgrid.exe   sptogp.exe    uvtovod.exe

If using the 'root' Dockerfile, the install location will be in /usr/local and not the home directory of the 'oifs' user.

In order to run the acceptance test as the root user the file t21test/job needs editing:

EXPID=epc8
MASTER=/usr/local/bin/master.exe

In order to run the executable with the command mpirun as root the following option needs to be added:  $OIFS_RUNCMD --allow-run-as-root $MASTER -e $EXPID

Sub-directories are allowed however symbolic links to other file system locations will not work; the symbolic links created by oifs_run at its first run will need to be manually created as sub-directories.

docker run -v /scratch/user/exp:/home/oifs/exp:rw -it oifs43r3v1.user

1. set:  export OIFS_EXE=/home/oifs/oifs43r3v1/make/gnu-opt/oifs/bin/master.exe     #  or wherever your master.exe is located

2. comment out the code block that checks for the OIFS executable:  ###if [ -d "$OIFS_EXE" ]; then ..... fi
3. do not copy the executable:   ##\cp -f "$OIFS_EXE" . || true
4. replace the call of the RUNCMD:
   Remove this line:
     $RUNCMD ./$(basename "$OIFS_EXE") || {
   and replace with this line:
     docker run -v /scratch/user/exp/:/home/oifs/exp:rw <oifs_image> bash -c "cd exp && ulimit -s unlimited && $OIFS_EXE" || {

<oifs_image> is the name of the OpenIFS docker image. You may need to adjust the directories used above depending on your docker image.
   

sudo systemctl start docker
sudo systemctl restart docker
sudo systemctl status docker

docker images
docker rmi oifs                       # remove image oifs, might need -f option 
docker rmi $(docker images -qa)       # removes all images, might need -f option 
docker save -o oifs_image.tar oifs    # saves image oifs to a tar file 
docker load -i oifs_image.tar         # loads saved docker image into memory

docker ps
docker ps -a                # show all containers
docker rm 6skd897asd        # removes container beginning with 6sk...
docker rm $(docker ps -qa)  # removes all containers, might need -f option

docker build -t <image name>  .                   # uses file called Dockerfile 
docker build -t <image name> -f <docker file>

At ECMWF, use the proxy arguments: 
docker build -t oifs --build-arg http_proxy="$http_proxy" --build-arg ftp_proxy="$ftp_proxy" --build-arg https_proxy="$https_proxy" --build-arg no_proxy="$no_proxy" .

docker run -it ubuntu                                # run interactively with tty output
docker run -it oifs                                  # run image oifs interactively
docker run -v /scratch/user:/scratch:rw -it oifs                                       # mount volume $SCRATCH inside container
docker run -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=unix$DISPLAY metview metview    # allows Metview to open X Window from inside the container