Apache Ignite Issue Under ECS Fargate

I am running the Apache Ignite Server in a Docker Container and have mounted a location to stored cached data.

Step 1:

I started the service using below command

docker run -d --name ignitedocker -p 10800:10800 \
-v /home/user/Documents/ignite_second/data:/opt/ignite/data \
-v /home/user/Documents/ignite_second/wal:/opt/ignite/apache-ignite/work/db/wal \
-v /home/user/Documents/ignite_second/wal/archive:/opt/ignite/apache-ignite/work/db/wal/archive \
-e IGNITE_FORCE_RECOVERY_MODE=true apache/ignite:apache-ignite-2.16.0-0.4

Apache Ignite service is up and running

Step 2 :

If I execute the below commands.

docker stop containerId and
docker start containerId

still I am able to retrieve the cached data using Apache Ignite. Reason being same container and container Id is being used.

Step 3:

However, when the Docker container ID changes (When we are removing/deleting the container and creating the new container pointing to same cached location ), we are unable to retrieve the cached data, even though Apache Ignite is running.

Are there any limitations or issues when using different Docker container IDs? Does Apache Ignite have tight coupling with docker containers.

Start by reproducing the two Docker workflows using the shown apache/ignite:apache-ignite-2.16.0-0.4 command and the mounted data and WAL paths. Compare Ignite startup and recovery logs after stopping and restarting the same container versus deleting it and creating a new one; done means the container-ID dependency and any required persistence configuration are documented.

Written by the indexing model from the issue text.