The Fan-Out Driver Shim Container requires pre-installation, installation, and post-installation work. Use the information in this section as you prepare to deploy the Fan-Out Driver shim container.
Navigate to the location where you have extracted the NIdM_Integration_Module_4.8.7_LinuxUnix_Containers.tar.gz file.
Navigate to the docker-images directory.
Run the following command to load the image:
docker load --input IDM_4870_asamcdrv.tar.gz
Verify you have the image loaded in your local image repository:
docker image ls asamcdrv:4.8.7.0000
Docker containers are intended to be disposed whenever you need to change container configurations or upgrade the base image software. Your Fan-Out Driver shim container will create and use custom configuration files, keys and log files that should be maintained in a data store that will persist across container rebuilds. Docker allows you to persist data for containers using volumes. Volumes can be created and maintained by docker, or the host can provide a file path for a volume, called a bind-mounted volume.
The examples used in this guide assumes that you are using a bind-mounted, volume located at /data on your Docker host. This path will be mapped to, and seen by, your container as /config.
mkdir /data
However, you can use other volumes that Docker supports. On some systems, using a Docker-created volume can give you a read/write performance improvement. For more details about Docker volumes, see https://docs.docker.com/storage/volumes/
Here are some important files and directories that are persisted by the Docker volume:
/config/ASAM/debug.log
/config/ASAM/keys/
/config/ASAM/setup/install.log
/config/ASAM/data/fanout.conf
/config/ASAM/data/CoreDriver/logs/
/config/ASAM/data/CoreDriver/certs/
/config/ASAM/rules/Fan-Out-IDM3_6_0-V1.xml