Vaultwarden server failed on arm64v8 platform

Third Party Help
1

Hello,
I deploy the arm64v8 docker container on ASUSTOR NAS for a long time, and the app works well till the recently version.
While I update to vaultwarden 1.28.1, the container can run successfully anymore.
The log of the container is as the followings.

/--------------------------------------------------------------------
| Starting Vaultwarden |

Version 1.28.1
This is an unofficial Bitwarden implementation, DO NOT use the
official channels to report bugs/features, regardless of client.
Send usage/configuration questions or feature requests to:
dani-garcia/vaultwarden · Discussions · GitHub or
https://vaultwarden.discourse.group/
Report suspected bugs/issues in the software itself at:
Sign in to GitHub · GitHub
--------------------------------------------------------------------/

Error loading config:
** SQLite database directory data does not exist or is not a directory**

I didn’t change any configuration to deploy the container.
The same Vaultwarden server 1.28.1 works well if using MariaDB or PostgreSQL database.

Could anyone help on this?
Thanks a lot!!

2

You probably have a wrong config for your sqlite file or your data folder is not correct. I suggest to check the config.

Keep in mind that all the config needs to be done from the point of view from within the container.

3

I didn’t change any config while deploy the container from beginning till now.
But, I just encounter this issue at recently version.
For SQLite, I didn’t bind host folder for it, and I bind another host folder for /data of the Vaultwarden.

Is there any config needed for SQLite?
And same configuration works well on amd64 platform from beginning till now.

4

Could you provide the docker config you used to run these containers?

5

Hello,
(If I change the tag to 1.27.0) ,and then the container can be start correctly, and works as the before.
Change to 1.28.0 and then latest (1.29.0 now), the failed log will be there after start the container.

docker create -i -t --name=Vaultwarden
-p 32301:80
-e ROCKET_TLS=‘{certs=“/ssl/ssl.crt”,key=“/ssl/ssl.key”}’
-e ADMIN_TOKEN=$ADMINTOKEN
-e LOG_FILE=‘/data/bitwarden_rs.log’
-e LOG_LEVEL=warn
-v /usr/builtin/etc/certificate/:/ssl/:ro
-v /etc/localtime:/etc/localtime:ro
-v /share/Docker/Vaultwarden/bw-data:/data:rw
–restart unless-stopped
vaultwarden/server:latest

docker start Vaultwarden

Thanks a lot.

6

It might be that you have a config.json in your data folder which for some reason has a strange setting for the database location? By default it will use main /data directory which you have created.

I tried using a symlink and an actual forlder, it all seems to work for me.
There probably is something else which is causing this, but i can’t reproduce this.

7

Hello,
Even I remove the /share/Docker/Vaultwarden/bw-data on the host, and re-bind the /data to a empty folder, the issue is still there.
I don’t know why!

** SQLite database directory data does not exist or is not a directory**

8

The issue is gone on 1.30.1 now.