Node (in docker) memory increase 4GB+ leading to container restart (v1.111.4)

[Alexey]

@RozzNL

Error: Error starting master database on storage node: Cannot acquire directory lock on "config/storage/filestatcache".  Another process is using this Badger database. error: resource temporarily unavailable

Since you enabled a badger cache, it cannot allow access from multiple processes.
To avoid such a problem you need to enable the badger cache not in the config file but as a command line option after the image name in your docker run command, i.e.

@Dr.Ko

--pieces.file-stat-cache=badger \
--pieces.enable-lazy-filewalker=false

The issue-apikey command wouldn’t throw an error, see

Badger cache: are we ready?

This need to be investigated. I wouldn’t expect it to be corrupted due to a normal restart. By the way, I accidentally found a solution for the docker node when the badger cache is enabled: you shouldn’t enable the badger cache in the config.yaml file, you need to use a command line option after the image name, so when you exec the key issue command in the docker container, it didn’t try to lock a filecache, because it’s not enabled in the config. This also explains why it works for my Doc…

However, you may also try this way:

docker exec -it Storagenode /app/storagenode info --log.output stdout --config-dir config --identity-dir identity --pieces.file-stat-cache=