Restart loop because of "Fatal error: piecestore monitor: disk space requirement not met"

[luca.berte98]

It returns 2 instances, the second with “Bad message”

@Alexey

You should mount a right path to the container.

How can I do it?

[Alexey]

Please, post paths to your instances and we will try to figure out a right one

[luca.berte98]

Here it is
/home/jubau/0storjnode/storage/info.db find:/home/jubau/0storjnode/storage/blobs/v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa/4l’: Bad message

[Alexey]

Please, show the output of the command

docker inspect storagenode -f '{{ .Mounts }}'

[luca.berte98]

Here we are
[{bind /home/jubau/0storjnode /app/config true rprivate} {bind /home/jubau/storj/storagenode_keys /app/identity true rprivate} {volume 5f6f3d117affbe0a1cb89badb61ba73cea29b18391589c4106badb9ce3a49fe9 /var/lib/docker/volumes/5f6f3d117affbe0a1cb89badb61ba73cea29b18391589c4106badb9ce3a49fe9/_data /root/.local/share/storj/storagenode local true }]

[Alexey]

You doesn’t have other copies of the info.db.
Have you replaced the -v options in your docker run command with the --mount?
Please, show the output of the command:

df -h

and

cat /etc/fstab

[luca.berte98]

@Alexey

df -h

---

@Alexey

cat /etc/fstab

Here is the output:
UUID=8cac60dc-c714-11e8-a67a-b870f4913702 / ext4 defaults 0 0
/swap.img none swap sw 0 0

[luca.berte98]

@Alexey

Have you replaced the -v options in your docker run command with the --mount ?

I have already done it!