writing issues #2213

New Issue

OVERLORD · 2025-10-09T17:51:29+03:00

OVERLORD commented

2025-10-09 17:51:29 +03:00

Originally created by @Homer-Sim on GitHub.

a question to the bitwarden container

I did not specify a user in docker command and databeses are running as root
-rw-r--r-- 1 root root 770048 Jan 19 17:35 db.sqlite3
-rw-r--r-- 1 root root 32768 Jan 19 19:08 db.sqlite3-shm
-rw-r--r-- 1 root root 8272 Jan 19 19:08 db.sqlite3-wal
drwxr-xr-x 2 root root 20480 Jan 16 19:39 icon_cache
-rw------- 1 root root 1192 Jan 15 23:20 rsa_key.der
-rw------- 1 root root 1679 Jan 15 23:20 rsa_key.pem
-rw-r--r-- 1 root root 270 Jan 15 23:20 rsa_key.pub.der

reading is possible with the browser app but not writing ...
Is there an addition to do in docker command?

Thanks

Originally created by @Homer-Sim on GitHub. a question to the bitwarden container I did not specify a user in docker command and databeses are running as root -rw-r--r-- 1 root root 770048 Jan 19 17:35 db.sqlite3 -rw-r--r-- 1 root root 32768 Jan 19 19:08 db.sqlite3-shm -rw-r--r-- 1 root root 8272 Jan 19 19:08 db.sqlite3-wal drwxr-xr-x 2 root root 20480 Jan 16 19:39 icon_cache -rw------- 1 root root 1192 Jan 15 23:20 rsa_key.der -rw------- 1 root root 1679 Jan 15 23:20 rsa_key.pem -rw-r--r-- 1 root root 270 Jan 15 23:20 rsa_key.pub.der reading is possible with the browser app but not writing ... Is there an addition to do in docker command? Thanks

OVERLORD closed this issue

2025-10-09 17:51:30 +03:00

OVERLORD commented

2025-10-09 17:51:32 +03:00

@mprasil commented on GitHub:

Great to hear. The bitwarden_rs itself doesn't have to run as root, in fact when I run it outside of container I never ran it as root, but there are some issues running the container as non root that I haven't time to look into yet. See #287

@mprasil commented on GitHub: Great to hear. The bitwarden_rs itself doesn't have to run as root, in fact when I run it outside of container I never ran it as root, but there are some issues running the container as non root that I haven't time to look into yet. See #287

OVERLORD commented

2025-10-09 17:51:32 +03:00

@Homer-Sim commented on GitHub:

OMG, I guess mistake was on my side. I am used to do docker command with autostart option. I missed it here and yes, it was not reachable because container was not running.

Sorry.

But does this container has to run as root?

@Homer-Sim commented on GitHub: OMG, I guess mistake was on my side. I am used to do docker command with autostart option. I missed it here and yes, it was not reachable because container was not running. Sorry. But does this container has to run as root?

OVERLORD commented

2025-10-09 17:51:32 +03:00

@mprasil commented on GitHub:

It sounds like the proxy might be misconfigured. The proxy error sounds like Caddy can't reach the backend. Is it possible that even reading is not working but the old data is served from cache?

Can you see any logs on bitwarden_rs side?

@mprasil commented on GitHub: It sounds like the proxy might be misconfigured. The proxy error sounds like Caddy can't reach the backend. Is it possible that even reading is not working but the old data is served from cache? Can you see any logs on bitwarden_rs side?

OVERLORD commented

2025-10-09 17:51:33 +03:00

@Homer-Sim commented on GitHub:

Maybe some interesting thing to add.

BW is running behind a Caddy reverse proxy and I have this error entry in the logs

ERROR 502 /identity/connect/token] dial tcp 192.168.100.10:8040: connect: connection refused

I hope you know to help me a little

@Homer-Sim commented on GitHub: Maybe some interesting thing to add. BW is running behind a Caddy reverse proxy and I have this error entry in the logs ERROR 502 /identity/connect/token] dial tcp 192.168.100.10:8040: connect: connection refused I hope you know to help me a little

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#2213