The mount path of the persistent volume wasn't up to date with our file structure in the container. Thus, the data was not persisted properly across container restarts.
Also, now we explicitly set a path for the local storage of the node-persist module.
Additionally, since we observe mysterious restarts of the adapter-registry containers on kubernetes deployments we removed the resource limits to exclude this as a possible cause.
The mount path of the persistent volume wasn't up to date with our file structure in the container. Thus, the data was not persisted properly across container restarts. Also, now we explicitly set a path for the local storage of the node-persist module.
Additionally, since we observe mysterious restarts of the adapter-registry containers on kubernetes deployments we removed the resource limits to exclude this as a possible cause.