Hi Jon,
thanks for your response.
You are right, I'm talking about the Configuration Container.
If I create a snapshot, I can see it in the volume and it will be also available in the Config Container when it starts up after a compose up, but I need to apply the snapshot manually...
What do you mean with "publish"? Maybe I forgot a step at this point.
Regards
Andreas
------------------------------
Andreas Rühl
------------------------------
Original Message:
Sent: Wed October 13, 2021 10:29 AM
From: Jon Harry
Subject: Volumes for PolicyServer on Docker
Hi Andreas,
When you say "PolicyServer" I assume you're referring to the Configuration Container? This is container "isvaconfig" in the cookbook.
This container should have a persistent volume mounted at /var/shared which is where snapshots are written when you publish them.
As you configure your Verify Access system in the LMI, changes are made to the volatile container filesystem. If you stop and start the container these are maintained but if you delete the container (as happens with docker-compose down) then these changes will be lost.
To avoid this situation, before you delete the container you need to "publish" a snapshot... this will save it to the persistent volume.
When a new (empty) configuration container starts, it will read the snapshot if it's present and reestablish the state.
I hope this helps to explain how this works.
Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
Original Message:
Sent: Wed October 13, 2021 04:16 AM
From: Andreas Rühl
Subject: Volumes for PolicyServer on Docker
Hi,
I have set up a PolicyServer on Docker, like explained in the cookbook for docker. After a docker-compose down and up the settings (agreement, password, database configuration) are gone.
With directory do I have to bind to a volume to preserve these information?
Regards
Andreas
------------------------------
Andreas Rühl
------------------------------