Missing libmariadb error on startup with latest commit #495

New Issue

OVERLORD · 2026-02-04T21:12:40+03:00

OVERLORD commented

2026-02-04 21:12:40 +03:00

Originally created by @mpetrole on GitHub (Nov 17, 2019).

I was running an older version of Bitwarden_rs from around 6 months ago but I wanted to fix Safari integration so I decided to update to the latest version. I destroyed my existing containers and then pruned all images. I pulled the latest commit and built it following the wiki with the mysql build option (docker build -t bitwarden_rs --build-arg DB=mysql .). After finishing the build, I started it with docker-compose, using the same docker-compose file that I was running before. After startup, Bitwarden fails to load and I see /bitwarden_rs: error while loading shared libraries: libmariadb.so.3: cannot open shared object file: No such file or directory in the logs.

I did copy over my docker-compose file, Caddyfile, and bw-data folder contents from my old installation, but I checked and it didn't seem like there was any reason for any of those to cause this kind of error.

My environment is in AWS, I have an EC2 instance running the docker containers and I'm using bitwarden and caddy, then I have a MySQL RDS instance for the DB.

Thanks in advance for any help!

Originally created by @mpetrole on GitHub (Nov 17, 2019). I was running an older version of Bitwarden_rs from around 6 months ago but I wanted to fix Safari integration so I decided to update to the latest version. I destroyed my existing containers and then pruned all images. I pulled the latest commit and built it following the wiki with the mysql build option (docker build -t bitwarden_rs --build-arg DB=mysql .). After finishing the build, I started it with docker-compose, using the same docker-compose file that I was running before. After startup, Bitwarden fails to load and I see `/bitwarden_rs: error while loading shared libraries: libmariadb.so.3: cannot open shared object file: No such file or directory` in the logs. I did copy over my docker-compose file, Caddyfile, and bw-data folder contents from my old installation, but I checked and it didn't seem like there was any reason for any of those to cause this kind of error. My environment is in AWS, I have an EC2 instance running the docker containers and I'm using bitwarden and caddy, then I have a MySQL RDS instance for the DB. Thanks in advance for any help!

OVERLORD closed this issue

2026-02-04 21:12:48 +03:00

OVERLORD commented

2026-02-04 21:13:02 +03:00

@dani-garcia commented on GitHub (Nov 20, 2019):

If you want to use a different database, you need to use the separate images, the main dockerfile is only for SQLite, because it's missing the correct dependencies. Try using something like:

docker build -t bitwarden_rs -f docker/amd64/mysql/Dockerfile .

@dani-garcia commented on GitHub (Nov 20, 2019): If you want to use a different database, you need to use the separate images, the main dockerfile is only for SQLite, because it's missing the correct dependencies. Try using something like: ``` docker build -t bitwarden_rs -f docker/amd64/mysql/Dockerfile . ```

OVERLORD commented

2026-02-04 21:13:09 +03:00

@mpetrole commented on GitHub (Nov 28, 2019):

Sorry for the late response, but that worked, thanks!

@mpetrole commented on GitHub (Nov 28, 2019): Sorry for the late response, but that worked, thanks!

OVERLORD commented

2026-02-04 21:13:20 +03:00

@ToeiRei commented on GitHub (Mar 15, 2020):

Wouldn't that be something for the documentation?

@ToeiRei commented on GitHub (Mar 15, 2020): Wouldn't that be something for the documentation?

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#495