wrfhydro/dev repository overview

WRF-HYDRO

Containers used for WRF-Hydro development. These containers are also suitable options for running WRF-Hydro simulations on a single-node system. See sub-tags (e.g. 'base', 'conda') for details on each container.

⁠latest

⁠Overview

This container is used for WRF-Hydro development and single-node WRF-Hydro simulations.

This container includes the following:

• Everything in wrfhydro/dev:base
• Python packages and other tools for development

⁠Usage

Step 1: Pull the image

$ docker pull wrfhydro/dev
or
$ docker pull wrfhydro/dev:latest

Step 2: Run the image

$ docker run -it wrfhydro/dev
or
$ docker run -it wrfhydro/dev:latest

Optionally: Run the image with a volume mount

NOTE: DO NOT COMPILE WRF-HYDRO IN THE MOUNTED FOLDER. On some filesystems, WRF-Hydro will not compile correctly if compilation occurs in a mounted directory. WRF-Hydro will run in a mounted directory on most filesystems, but compilation may fail.

docker run -v <path-to-your-local-mount-folder>:<path-to-the-desired-docker-folder> -it wrfhydro/dev

⁠base

⁠Overview

This container is used for WRF-Hydro development and single-node WRF-Hydro simulations.

This container includes the following:

• Ubuntu base image
• All system libraries required by WRF-Hydro
• Text editors - VIM, Nano, Emacs
• git version control system
• nccmp - NetCDF Compare utility for diffing NetCDF files
• NetCDF C and Fortran libraries
• MPI

⁠Usage

Step 1: Pull the image

docker pull wrfhydro/dev:base

Step 2: Run the image

docker run -it wrfhydro/dev:base

Optionally: Run the image with a volume mount

NOTE: DO NOT COMPILE WRFHYDRO IN THE MOUNTED FOLDER. On some filesystems, WRF-Hydro will not compile correctly if compilation occurs in a mounted directory. WRF-Hydro will run in a mounted directory on most filesystems, but compilation may fail.

docker run -v <path-to-your-local-mount-folder>:<path-to-the-desired-docker-folder> -it wrfhydro/dev:base

⁠sudo

The Docker images do not provide sudo privileges to the user due to security best practices. If additional privileges are needed the user can edit and build the Docker files under dev/latest⁠ or dev/base⁠. The user will need to first remove the USER docker line at the end of the Dockerfile.