[GH-ISSUE #351] Question: Docker-compose and bitwarden_rs only on RasPi #197

New issue

Closed

opened 2026-03-03 01:26:34 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 01:26:34 +03:00

Owner

Originally created by @MeiRos on GitHub (Jan 19, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/351

I'm not sure if this is a good place to talk about this or not. But please. show me other place, if I should change place.

I was about to use bitwarden_rs on VPS but then I decided to move it to my my home network and on Raspberry pi. I had some test settings on VPS which I moved to Rpi. So, I'm going to run this with docker-compose, because settings were quite ready. Is it bad or good idea? There's no need for proxy so there's only Bitwarden image.
I have issued Let's Encrypt certificate with acme.sh. I used DNS alias mode. Maybe this is not needed but now it's secure connection at home. I have to use https://home.example.com to connect securelly.
My docker-compose.yml is:

#docker-compose.yml
version: '3'
services:
 bitwarden:
  image: mprasil/bitwarden:raspberry
  restart: always
  volumes:
      - ./bw-data/:/data/
      - /home/pi/ssl/:/ssl/
  environment:
   ROCKET_TLS: '{certs = "/ssl/fullchain.pem", key = "/ssl/key.pem"}'
   SIGNUPS_ALLOWED: "true"
   SMTP_HOST: "smtp.host.net"
   SMTP_FROM: "no-reply@home.example.com"
   SMTP_PORT: "587"
   SMTP_SSL: "true"
   SMTP_USERNAME: "xxx"
   SMTP_PASSWORD: "yyy"
   LOG_FILE: "/data/bitwarden.log"
  ports:
      - 192.168.1.20:443:80 #Raspberry's home IP

What do you think? Can this work properly?
If this is ok, I can add this to wiki.
Because I'm noob with docker, how do I update bitwarden image? Just docker-compose down and then up -d ?

Originally created by @MeiRos on GitHub (Jan 19, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/351 I'm not sure if this is a good place to talk about this or not. But please. show me other place, if I should change place. I was about to use bitwarden_rs on VPS but then I decided to move it to my my home network and on Raspberry pi. I had some test settings on VPS which I moved to Rpi. So, I'm going to run this with docker-compose, because settings were quite ready. Is it bad or good idea? There's no need for proxy so there's only Bitwarden image. I have issued Let's Encrypt certificate with acme.sh. I used DNS alias mode. Maybe this is not needed but now it's secure connection at home. I have to use https://home.example.com to connect securelly. My docker-compose.yml is: ``` #docker-compose.yml version: '3' services: bitwarden: image: mprasil/bitwarden:raspberry restart: always volumes: - ./bw-data/:/data/ - /home/pi/ssl/:/ssl/ environment: ROCKET_TLS: '{certs = "/ssl/fullchain.pem", key = "/ssl/key.pem"}' SIGNUPS_ALLOWED: "true" SMTP_HOST: "smtp.host.net" SMTP_FROM: "no-reply@home.example.com" SMTP_PORT: "587" SMTP_SSL: "true" SMTP_USERNAME: "xxx" SMTP_PASSWORD: "yyy" LOG_FILE: "/data/bitwarden.log" ports: - 192.168.1.20:443:80 #Raspberry's home IP ``` What do you think? Can this work properly? If this is ok, I can add this to wiki. Because I'm noob with docker, how do I update bitwarden image? Just docker-compose down and then up -d ?

kerem closed this issue

2026-03-03 01:26:35 +03:00

kerem commented

2026-03-03 01:26:35 +03:00

Author

Owner

@mprasil commented on GitHub (Jan 19, 2019):

Not sure if I understood your question correctly, but technically speaking the only difference should be the different (raspberry) image being used. You might need to use different DNS setup, but this has nothing to do with running on raspberry and is just specific to your network.

@mprasil commented on GitHub (Jan 19, 2019): Not sure if I understood your question correctly, but technically speaking the only difference should be the different (raspberry) image being used. You might need to use different DNS setup, but this has nothing to do with running on raspberry and is just specific to your network.

kerem commented

2026-03-03 01:26:35 +03:00

Author

Owner

@MeiRos commented on GitHub (Jan 19, 2019):

Well, there are many questions. ;)
Sorry for unclear questions.
Is it ok to run single image with docker-compose? Like now there's no proxy image included.
Do I need to add something to my docker-compose.yml file or should it work now properly and securely so it can be added to wiki as an single image example for docker-compose?
Do I get updated image if I do 'docker-compose down' and 'docker-compose up -d'?
Hopefully I have more clear questions now.

Let's Encrypt part is more like telling about environment where the Bitwarden is running. So no questions about it.

Thank You! You are doing great job dani-garcia, mprasil and others.

@MeiRos commented on GitHub (Jan 19, 2019): Well, there are many questions. ;) Sorry for unclear questions. Is it ok to run single image with docker-compose? Like now there's no proxy image included. Do I need to add something to my docker-compose.yml file or should it work now properly and securely so it can be added to wiki as an single image example for docker-compose? Do I get updated image if I do 'docker-compose down' and 'docker-compose up -d'? Hopefully I have more clear questions now. Let's Encrypt part is more like telling about environment where the Bitwarden is running. So no questions about it. Thank You! You are doing great job dani-garcia, mprasil and others.

kerem commented

2026-03-03 01:26:36 +03:00

Author

Owner

@mprasil commented on GitHub (Jan 19, 2019):

Ah I see what you mean now. Yes, you can use docker compose for single container. If you add it to wiki, I'd suggest providing example with x86 image though. Having raspberry image there for no real reason could be confusing.

Running without proxy is fine, but if you want to get websockets synchronisation working, you'll need proxy.

As for updating the image, you need to run docker-compose pull before running the up command.

Hope that helps.

@mprasil commented on GitHub (Jan 19, 2019): Ah I see what you mean now. Yes, you can use docker compose for single container. If you add it to wiki, I'd suggest providing example with x86 image though. Having raspberry image there for no real reason could be confusing. Running without proxy is fine, but if you want to get websockets synchronisation working, you'll need proxy. As for updating the image, you need to run `docker-compose pull` before running the `up` command. Hope that helps.

kerem commented

2026-03-03 01:26:36 +03:00

Author

Owner

@mprasil commented on GitHub (Jan 28, 2019):

Going to close this one as I believe the question was answered.

@mprasil commented on GitHub (Jan 28, 2019): Going to close this one as I believe the question was answered.