Fix persistent folder check within containers #2050

New Issue

MrUnknownDE · 2026-04-06T02:51:21+02:00

MrUnknownDE commented

2026-04-06 02:51:21 +02:00

Originally created by @BlackDex on 7/19/2022

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

*Originally created by @BlackDex on 7/19/2022* 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

MrUnknownDE closed this issue

2026-04-06 02:51:21 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#2050