9a787dd105
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 |
||
|---|---|---|
| .. | ||
| Dockerfile | ||
| Dockerfile.alpine | ||
| Dockerfile.buildx | ||
| Dockerfile.buildx.alpine | ||