IBM Verify

 View Only

 Looking for help configuring ISVD Seed container

Jump to  Best Answer
Michael Kochenburger's profile image
Michael Kochenburger posted Wed July 23, 2025 03:37 AM
Hi,
 
I am currently trying to set up an ISVD demo container environment with Docker on virtual machines to understand how it works and can then be used by our customer. I'm currently lacking an understanding of how the seed container works, as the documentation provides insufficient information on this.
 
1)
I mount the volume /var/isvd/source like this:
 
     docker run \
         --hostname isvd-seed \
         --name isvd-seed \
         --detach \
         --volume /var/isvd/source:/var/isvd/source \
         --volume /var/isvd/data:/var/isvd/data \
         --volume /var/isvd/config:/var/isvd/config \
         --env YAML_CONFIG_FILE=/var/isvd/config/config-seed.yaml \
         --env LANG=C \
         icr.io/isvd/verify-directory-seed:10.0.4.0
 
When the seed container is started, 'docker ps' indicates that it is 'unhealthy'. However, no error is displayed in the log and the last message is:
 
GLPCON024I Waiting for the .md5 and .ldif files to appear in the '/var/isvd/source' directory
 
However, if you copy an .ldif file to /var/isvd/source, absolutely nothing happens. If the .ldif file already exists before the container is started, nothing happens either.
 
2)
If this all works, what is the best way to recognise when the seed import is complete and successful?
 
3)
Is it possible to establish an ssh connection to the container by means of a corresponding configuration setting?
 
     $ docker inspect -f '{{ .NetworkSettings.IPAddress }}' isvd-seed
     172.17.0.3
     $ telnet 172.17.0.3
     Trying 172.17.0.3...
     telnet: Unable to connect to remote host: Connection refused
 
I hope that this will make it easier to understand how the seed container works if you can log in via ssh.

Scott Exton's profile image
Scott Exton posted Wed July 23, 2025 05:19 PM  Best Answer

Michael,

The documentation contains the answers to the majority of your questions (see: https://www.ibm.com/docs/en/svd/10.0.4?topic=scenarios-migration-from-software).   However, to directly answer your questions:

1) You need to copy both the .ldif file, and an .md5 file which contains an md5 checksum of the .ldif file.  The .md5 file is used by the seed container to check that the complete ldif file is available before it commences processing the file.

2) Monitor the log output of the container.  The container will stop when it has completed the processing of the files.

3) Generally you don't use ssh to connect to a container.  Instead you use the native 'docker exec' or 'kubectl exec' commands to establish a shell on the container.

I hope that this helps.

Scott.

Related Content