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 Docker node , because I enabled it exactly like that, because it’s more convenient if you use a docker compose:
services: (3/3 results) [1190/2149]
storagenode2:
container_name: storagenode2
restart: always
stop_grace_period: 300s
image: storjlabs/storagenode:latest
...
command:
- --pieces.enable-lazy-filewalker=false
- --pieces.file-stat-cache=badger
# - --healthcheck.details=true
# - "--operator.wallet-features=zksync"