mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-08-24 23:22:58 -05:00
Problem with starting docker bitwarden #3986
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vaultwarden#3986
Reference in New Issue
Block a user
Originally created by @LeoArnts on GitHub (Jul 23, 2019).
After a restart of the Ubuntu server and starting the docker bitwarden i get the following error:
docker: Error response from daemon: error while creating mount source path '/bw-data': mkdir /bw-data: read-only file system.
Does someone have a solution ?
Regards,
Leo
@mprasil commented on GitHub (Jul 24, 2019):
It sounds like you have your filesystem mounted read-only. Could be corrupted filesystem or something similar. Can you create the directory yourself? (
sudo mkdir /bw-data)@mprasil commented on GitHub (Jul 26, 2019):
Have you figured out the problem?
@mprasil commented on GitHub (Jul 28, 2019):
Hi, I hope you figured the issue and this is now solved. I'm going to close this as there was no response for couple days. Feel free to reopen if you still experience problems.
@LeoArnts commented on GitHub (Jul 30, 2019):
Sorry the problem was gone after an update of docker in Ubuntu. But its back again.
@LeoArnts commented on GitHub (Jul 30, 2019):
root@docker:
# docker pull bitwardenrs/server:latest# docker run -d --name bitwarden -v /bw-data/:/data/ -p 80:80 bitwardenrs/server:latestlatest: Pulling from bitwardenrs/server
Digest: sha256:52f309e4deccd2191b1985a462651990dbe6ac324b4e29394c93e0cd0686bb47
Status: Image is up to date for bitwardenrs/server:latest
docker.io/bitwardenrs/server:latest
root@docker:
6837e21a5fba10b799c66f563b5ef1fb86200f58e5a32168b222ef320d9dc611
docker: Error response from daemon: error while creating mount source path '/bw-data': mkdir /bw-data: read-only file system.
@mprasil commented on GitHub (Aug 1, 2019):
This seems to be some local system issue. I'd check the filesystem and drive maybe.
@ghost commented on GitHub (Dec 2, 2021):
Had the same problem using Ubuntu 20.04.3 with preinstalled docker option on a Proxmox vm.
The solution in my case was to simply run the command with /root/vw-data instead of /vw-data.
Don't know why, but worked.