starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00

[GH-ISSUE #686] Issue with mounting directories as a data volume #464

New issue

Closed

opened 2026-03-03 01:29:24 +03:00 by kerem · 5 comments

kerem commented

2026-03-03 01:29:24 +03:00

Owner

Originally created by @deeztek on GitHub (Oct 27, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/686

I realize this is probably an odd issue, I'm wanting to deploy bitwardenrs on Vsphere Integrated Containers. One of the limitations with VIC that I'm running into is the fact that you are not able to mount directories as a data volume. So, including the -v option for persistent storage in the command below fails:

docker run -d --name bitwarden -v /bw-data/:/data/ -p 80:80 bitwardenrs/server:latest

If I don't use the -v option, the container gets created successfully, but I'm assuming that I don't have persistent storage at at that point. One of the workarounds is to create a volume before-hand and then use that in the container. So, I created a bw-data volume, but I'm not really clear on how to integrate that into bitwardenrs.

I would appreciate some help on this.

Thanks a lot!

Originally created by @deeztek on GitHub (Oct 27, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/686 I realize this is probably an odd issue, I'm wanting to deploy bitwardenrs on Vsphere Integrated Containers. One of the limitations with VIC that I'm running into is the fact that you are not able to mount directories as a data volume. So, including the -v option for persistent storage in the command below fails: docker run -d --name bitwarden -v /bw-data/:/data/ -p 80:80 bitwardenrs/server:latest If I don't use the -v option, the container gets created successfully, but I'm assuming that I don't have persistent storage at at that point. One of the workarounds is to create a volume before-hand and then use that in the container. So, I created a bw-data volume, but I'm not really clear on how to integrate that into bitwardenrs. I would appreciate some help on this. Thanks a lot!

kerem closed this issue

2026-03-03 01:29:25 +03:00

kerem commented

2026-03-03 01:29:26 +03:00

Author

Owner

@dani-garcia commented on GitHub (Oct 27, 2019):

Can you try to remove the slashes from the left side of the : in the -v parameter?

Like this:

docker run -d --name bitwarden -v bw-data:/data -p 80:80 bitwardenrs/server:latest

I think Docker would interpret that as a volume name instead of a directory name.

@dani-garcia commented on GitHub (Oct 27, 2019): Can you try to remove the slashes from the left side of the `:` in the `-v` parameter? Like this: ``` docker run -d --name bitwarden -v bw-data:/data -p 80:80 bitwardenrs/server:latest ``` I think Docker would interpret that as a volume name instead of a directory name.

kerem commented

2026-03-03 01:29:26 +03:00

Author

Owner

@deeztek commented on GitHub (Oct 27, 2019):

Thanks for the suggestion. It seems to have worked, docker created the container successfully. The /data is a NFS share. So, I'm assuming the bw-data is now mapped to /data NFS share. What type of data/files should I be able to find there?

@deeztek commented on GitHub (Oct 27, 2019): Thanks for the suggestion. It seems to have worked, docker created the container successfully. The /data is a NFS share. So, I'm assuming the bw-data is now mapped to /data NFS share. What type of data/files should I be able to find there?

kerem commented

2026-03-03 01:29:26 +03:00

Author

Owner

@dani-garcia commented on GitHub (Oct 27, 2019):

Well the /data path is where the bw-data gets mounted inside the volume, not where it's mapped externally, I'm not sure how to access the data inside a docker volume directly.

About the structure, the important files are the db.sqlite3* files from the database, one attachments folder if you use them, and the config.json file if you use the admin page.

@dani-garcia commented on GitHub (Oct 27, 2019): Well the /data path is where the bw-data gets mounted inside the volume, not where it's mapped externally, I'm not sure how to access the data inside a docker volume directly. About the structure, the important files are the db.sqlite3* files from the database, one attachments folder if you use them, and the config.json file if you use the admin page.

kerem commented

2026-03-03 01:29:26 +03:00

Author

Owner

@mprasil commented on GitHub (Nov 5, 2019):

@deeztek did that answer your question?

@mprasil commented on GitHub (Nov 5, 2019): @deeztek did that answer your question?

kerem commented

2026-03-03 01:29:26 +03:00

Author

Owner

@deeztek commented on GitHub (Nov 5, 2019):

@mprasil yes. I was able to get everything working. Thanks a lot for the help!

@deeztek commented on GitHub (Nov 5, 2019): @mprasil yes. I was able to get everything working. Thanks a lot for the help!