Originally created by @sylvesterroos on GitHub (Jul 22, 2021).
Subject of the issue
Launching the vaultwarden container immediately crashes with the error message in the title.
Deployment environment
Install method: latest docker image
Other relevant details: I'm running the latest image on a raspberry pi running Ubuntu server 20.04 LTS.
Steps to reproduce
I set the data directory to be on my (which still has space for files) external hard drive. docker run -d --name vaultwarden -v /mnt/storage/Appdata/vaultwarden/:/data/ -p 8100:80 vaultwarden/server:latest
Originally created by @sylvesterroos on GitHub (Jul 22, 2021).
<!--
# ###
NOTE: Please update to the latest version of vaultwarden before reporting an issue!
This saves you and us a lot of time and troubleshooting.
See:
* https://github.com/dani-garcia/vaultwarden/issues/1180
* https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image
# ###
-->
<!--
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
Launching the vaultwarden container immediately crashes with the error message in the title.
### Deployment environment
<!-- How the server was installed: Docker image, OS package, built from source, etc. -->
* Install method: latest docker image
* Other relevant details: I'm running the latest image on a raspberry pi running Ubuntu server 20.04 LTS.
### Steps to reproduce
I set the data directory to be on my (which still has space for files) external hard drive.
`docker run -d --name vaultwarden -v /mnt/storage/Appdata/vaultwarden/:/data/ -p 8100:80 vaultwarden/server:latest`
### Expected behaviour
The container should launch without crashing
### Actual behaviour
Crash
### Troubleshooting data
docker logs vaultwarden:
[vaultwarden.log](https://github.com/dani-garcia/vaultwarden/files/6864394/log.log)
@RealOrangeOne commented on GitHub (Jul 22, 2021):
disk I/O error
Looks like it's an error with our disk, not vaultwarden.
Are you running other applications off the drive just fine? It's not about free space, it's more likely the drive is failing, corrupting, or a bad cable.
@RealOrangeOne commented on GitHub (Jul 22, 2021):
> disk I/O error
Looks like it's an error with our disk, not vaultwarden.
Are you running other applications off the drive just fine? It's not about free space, it's more likely the drive is failing, corrupting, or a bad cable.
I think you are using a shared storage like samba/cifs or nfs. For that to work you need to disable WAL. But i would suggest to use a different type of database in that case like postgresql or mariadb.
@BlackDex commented on GitHub (Jul 22, 2021):
I think you are using a shared storage like samba/cifs or nfs. For that to work you need to disable WAL. But i would suggest to use a different type of database in that case like postgresql or mariadb.
@sylvesterroos commented on GitHub (Jul 22, 2021):
The storage folder is indeed shared using samba. You're saying that not sharing this folder will fix the issue?
@sylvesterroos commented on GitHub (Jul 22, 2021):
The storage folder is indeed shared using samba. You're saying that not sharing this folder will fix the issue?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @sylvesterroos on GitHub (Jul 22, 2021).
Subject of the issue
Launching the vaultwarden container immediately crashes with the error message in the title.
Deployment environment
Install method: latest docker image
Other relevant details: I'm running the latest image on a raspberry pi running Ubuntu server 20.04 LTS.
Steps to reproduce
I set the data directory to be on my (which still has space for files) external hard drive.
docker run -d --name vaultwarden -v /mnt/storage/Appdata/vaultwarden/:/data/ -p 8100:80 vaultwarden/server:latestExpected behaviour
The container should launch without crashing
Actual behaviour
Crash
Troubleshooting data
docker logs vaultwarden:
vaultwarden.log
@RealOrangeOne commented on GitHub (Jul 22, 2021):
Looks like it's an error with our disk, not vaultwarden.
Are you running other applications off the drive just fine? It's not about free space, it's more likely the drive is failing, corrupting, or a bad cable.
@BlackDex commented on GitHub (Jul 22, 2021):
I think you are using a shared storage like samba/cifs or nfs. For that to work you need to disable WAL. But i would suggest to use a different type of database in that case like postgresql or mariadb.
@sylvesterroos commented on GitHub (Jul 22, 2021):
The storage folder is indeed shared using samba. You're saying that not sharing this folder will fix the issue?
@BlackDex commented on GitHub (Jul 22, 2021):
Not using a samba/cifs or nfs folder will solve your issue.