In this scenario, you already have the Fan-Out Driver shim installed and deployed somewhere, which has not been containerized. We will go through the procedure for migrating this installation into a containerized instance.
Your existing installation of the Fan-Out Driver Shim uses a directory to hold its certificates, keys, log and configuration files. Typically, this is located under /usr/local/ASAM, but it may have been changed as an install option. Locate this directory and, if necessary, copy it to the Docker host that you plan to deploy the containerized instance of it.
The following files will be migrated to the containerized volume:
keys/ca.pem
keys/lpwd1f40
keys/dpwd1f40
data/CoreDriver/certs/ca_cert.pem
data/CoreDriver/certs/ca_cert.key
data/CoreDriver/certs/ca.pem
For this step, we are going to assume your local installation directory was /usr/local/ASAM. Run the docker image with your local directory mapped to the /migrate input volume:
docker run -v /usr/local/ASAM:/migrate -v /data:/config -it asamcdrv:4.8.7.0000
Now that your existing installation has been migrated to a container, you can start the container instance.
docker run -d --ulimit nofile=8192 --name=asamcdrv-container --network=host -v /data:/config asamcdrv:4.8.7.0000 -d --ulimit nofile=8192 asamcdrv --network=host
You may now stop your current Driver Shim that is not running containerized.
systemctl stop asamcdrv
If the container is running on a Docker host with a different hostname IP or DNS name than the previous shim, we will need to change the Driver Properties to provide the appropriate connection parameters.
Login to Identity Console as an administrative user and click the Drivers module.
Locate and click the Fan-Out driver to edit.
Select the Connection Parameters tab.
Locate the Remote Loader Connection parameters.