BlackDex 9a787dd105
Fix persistent folder check within containers
The previous persistent folder check worked by checking if a file
exists. If you used a bind-mount, then this file is not there. But when
using a docker/podman volume those files are copied, and caused the
container to not start.

This change checks the `/proc/self/mountinfo` for a specific patern to
see if the data folder is persistent or not.

Fixes #2622
2022-07-20 13:29:39 +02:00
..
2020-03-25 20:13:36 -07:00
2021-09-13 14:42:15 +02:00
2020-07-15 20:03:34 -07:00

The arch-specific directory names follow the arch identifiers used by the Docker official images:

https://github.com/docker-library/official-images/blob/master/README.md#architectures-other-than-amd64