Installation instructions in README.md don't create persistent volume storage. #1967

Closed
opened 2026-02-05 02:24:24 +03:00 by OVERLORD · 0 comments
Owner

Originally created by @Zcehtro on GitHub (Jul 16, 2024).

Subject of the issue

The command docker run -d --name vaultwarden -v /vw-data/:/data/ --restart unless-stopped -p 80:80 vaultwarden/server:latest does not create a persistent volume.

Persistent storage is not implemented on creation of the container.

Deployment environment

  • vaultwarden version: 1.31.0
  • Install method: docker image

  • Other relevant details: ran via powershell core on Windows 10

Steps to reproduce

Run command found on README.md :

docker run -d --name vaultwarden -v /vw-data/:/data/ --restart unless-stopped -p 80:80 vaultwarden/server:latest

Expected behaviour

Creates the container and creates the docker volume with the appropriate binding.

Actual behaviour

Creates the container and does not create the volume.

Troubleshooting data

Fixed command that worked for me is on powershell core on Windows 10:

docker run -d --name vaultwarden -v vw-data:/data/ --restart unless-stopped -p 80:80 vaultwarden/server:latest

Basically remove the forward slashes from vw-data.

Originally created by @Zcehtro on GitHub (Jul 16, 2024). <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> The command `docker run -d --name vaultwarden -v /vw-data/:/data/ --restart unless-stopped -p 80:80 vaultwarden/server:latest` does not create a persistent volume. Persistent storage is not implemented on creation of the container. ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.31.0 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: docker image * Other relevant details: ran via powershell core on Windows 10 ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> Run command found on `README.md` : ```sh docker run -d --name vaultwarden -v /vw-data/:/data/ --restart unless-stopped -p 80:80 vaultwarden/server:latest ``` ### Expected behaviour Creates the container and creates the docker volume with the appropriate binding. ### Actual behaviour <!-- Tell us what actually happened --> Creates the container and does not create the volume. ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> Fixed command that worked for me is on powershell core on Windows 10: ```sh docker run -d --name vaultwarden -v vw-data:/data/ --restart unless-stopped -p 80:80 vaultwarden/server:latest ``` Basically remove the forward slashes from `vw-data`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1967