vaultwarden-test

Verlauf

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
..
amd64	Fix persistent folder check within containers	2022-07-20 13:29:39 +02:00
arm64	Fix persistent folder check within containers	2022-07-20 13:29:39 +02:00
armv6	Fix persistent folder check within containers	2022-07-20 13:29:39 +02:00
armv7	Fix persistent folder check within containers	2022-07-20 13:29:39 +02:00
Dockerfile.buildx	Update async to prepare for main merge	2022-02-22 20:00:33 +01:00
Dockerfile.j2	Fix persistent folder check within containers	2022-07-20 13:29:39 +02:00
healthcheck.sh	Healthcheck fixes/optimizations	2020-03-25 20:13:36 -07:00
Makefile	Optimize release workflow.	2021-09-13 14:42:15 +02:00
README.md	Multi-arch image support	2020-07-15 20:03:34 -07:00
render_template	Generate Dockerfiles from one source for maintainability. Closes #785 .	2019-12-28 22:52:20 +01:00
start.sh	Remove warning when compiling only with mysql and add compatibility mode with the old docker script names	2021-04-29 16:01:04 +02:00

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