Anyone use bitwarden in docker?

BlueCoffee · 15. Oktober 2023

Ive been looking at it and there compose is insane.

Code

#
# Useful references:
# https://docs.docker.com/compose/compose-file/
# https://docs.docker.com/compose/reference/overview/#use--f-to-specify-name-and-path-of-one-or-more-compose-files
# https://docs.docker.com/compose/reference/envvars/
#
#########################################################################
# WARNING: This file is generated. Do not make changes to this file.    #
# They will be overwritten on update. If you want to make additions to  #
# this file, you can create a `docker-compose.override.yml` file in the #
# same directory and it will be merged into this file at runtime. You   #
# can also manage various settings used in this file from the           #
# ./bwdata/config.yml file for your installation.                       #
#########################################################################

version: '3'

services:
  mssql:
    image: bitwarden/mssql:latest
    container_name: bitwarden-mssql
    restart: always
    stop_grace_period: 60s
    volumes:
      - ../mssql/data:/var/opt/mssql/data
      - ../logs/mssql:/var/opt/mssql/log
      - ../mssql/backups:/etc/bitwarden/mssql/backups
    env_file:
      - mssql.env
      - ../env/uid.env
      - ../env/mssql.override.env

  web:
    image: bitwarden/web:latest
    container_name: bitwarden-web
    restart: always
    volumes:
      - ../web:/etc/bitwarden/web
    env_file:
      - global.env
      - ../env/uid.env

  attachments:
    image: bitwarden/attachments:latest
    container_name: bitwarden-attachments
    restart: always
    volumes:
      - ../core/attachments:/etc/bitwarden/core/attachments
    env_file:
      - global.env
      - ../env/uid.env

  api:
    image: bitwarden/api:latest
    container_name: bitwarden-api
    restart: always
    volumes:
      - ../core:/etc/bitwarden/core
      - ../ca-certificates:/etc/bitwarden/ca-certificates
      - ../logs/api:/etc/bitwarden/logs
    env_file:
      - global.env
      - ../env/uid.env
      - ../env/global.override.env
    networks:
      - default
      - public

  identity:
    image: bitwarden/identity:latest
    container_name: bitwarden-identity
    restart: always
    volumes:
      - ../identity:/etc/bitwarden/identity
      - ../core:/etc/bitwarden/core
      - ../ca-certificates:/etc/bitwarden/ca-certificates
      - ../logs/identity:/etc/bitwarden/logs
    env_file:
      - global.env
      - ../env/uid.env
      - ../env/global.override.env
    networks:
      - default
      - public

  sso:
    image: bitwarden/sso:latest
    container_name: bitwarden-sso
    restart: always
    volumes:
      - ../identity:/etc/bitwarden/identity
      - ../core:/etc/bitwarden/core
      - ../ca-certificates:/etc/bitwarden/ca-certificates
      - ../logs/sso:/etc/bitwarden/logs
    env_file:
      - global.env
      - ../env/uid.env
      - ../env/global.override.env
    networks:
      - default
      - public

  admin:
    image: bitwarden/admin:latest
    container_name: bitwarden-admin
    restart: always
    depends_on:
      - mssql
    volumes:
      - ../core:/etc/bitwarden/core
      - ../ca-certificates:/etc/bitwarden/ca-certificates
      - ../logs/admin:/etc/bitwarden/logs
    env_file:
      - global.env
      - ../env/uid.env
      - ../env/global.override.env
    networks:
      - default
      - public

  icons:
    image: bitwarden/icons:latest
    container_name: bitwarden-icons
    restart: always
    volumes:
      - ../ca-certificates:/etc/bitwarden/ca-certificates
      - ../logs/icons:/etc/bitwarden/logs
    env_file:
      - global.env
      - ../env/uid.env
    networks:
      - default
      - public

  notifications:
    image: bitwarden/notifications:latest
    container_name: bitwarden-notifications
    restart: always
    volumes:
      - ../ca-certificates:/etc/bitwarden/ca-certificates
      - ../logs/notifications:/etc/bitwarden/logs
    env_file:
      - global.env
      - ../env/uid.env
      - ../env/global.override.env
    networks:
      - default
      - public

  events:
    image: bitwarden/events:latest
    container_name: bitwarden-events
    restart: always
    volumes:
      - ../ca-certificates:/etc/bitwarden/ca-certificates
      - ../logs/events:/etc/bitwarden/logs
    env_file:
      - global.env
      - ../env/uid.env
      - ../env/global.override.env
    networks:
      - default
      - public

  nginx:
    image: bitwarden/nginx:latest
    container_name: bitwarden-nginx
    restart: always
    depends_on:
      - web
      - admin
      - api
      - identity
    ports:
      - '80:8080'
      - '443:8443'
    volumes:
      - ../nginx:/etc/bitwarden/nginx
      - ../letsencrypt:/etc/letsencrypt
      - ../ssl:/etc/ssl
      - ../logs/nginx:/var/log/nginx
    env_file:
      - ../env/uid.env
    networks:
      - default
      - public


networks:
  default:
    internal: true
  public:
    internal: false

Alles anzeigen

I have no idea where to even start to select my own paths. Docker check fails on the default compose. Anyone use it and had success?

nonmaterialistically · 15. Oktober 2023

Yeah, their "full deploy" has been daunting to use for a while. I used their deploy script to deploy it on a dedicated VM, just to avoid the gigantic compose.

They have had a new "unified container" out in beta for almost a year, which restricts the deploy to 2 containers (bitwarden + db). Check the documentation page and the issues status page. I'd suggest trying either that or (if you're not using many of the enterprise features) vaultwarden.

BlueCoffee · 15. Oktober 2023

Zitat von nonmaterialistically

Yeah, their "full deploy" has been daunting to use for a while. I used their deploy script to deploy it on a dedicated VM, just to avoid the gigantic compose.
They have had a new "unified container" out in beta for almost a year, which restricts the deploy to 2 containers (bitwarden + db). Check the documentation page and the issues status page. I'd suggest trying either that or (if you're not using many of the enterprise features) vaultwarden.

Aye I was thinking about that also. Ill run in it in a KVM. Cheers

macom · 15. Oktober 2023

Vaultwarden is easy to setup in docker.

BlueCoffee · 15. Oktober 2023

Zitat von macom

Vaultwarden is easy to setup in docker.

How so? Do you use NPM with it?

macom · 15. Oktober 2023

Nope, SWAG

BlueCoffee · 15. Oktober 2023

Doesn't look like there is an option for NPM.

Proxy examples

Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs - dani-garcia/vaultwarden

github.com

BlueCoffee · 15. Oktober 2023

Got it working thanks looks good

chente · 15. Oktober 2023

If you want to explore alternatives, I use KePassXC for passwords. Without containers or internet services, you just need to sync a file between your clients any way you want. https://keepassxc.org/

BlueCoffee · 15. Oktober 2023

Zitat von chente

If you want to explore alternatives, I use KePassXC for passwords. Without containers or internet services, you just need to sync a file between your clients any way you want. https://keepassxc.org/

Ive used keepass for years never liked XC https://keepass.info/

chente · 15. Oktober 2023

I didn't like Keepass either. KeePassXC is different.

macom · 15. Oktober 2023

Cool thing is, you can use the same database with Keepass and KeePassXC. We have Keepass at work and I have KeePassXC on my private laptop, so I can use the same database at work and on my home laptop and tablet.

KM0201 · 16. Oktober 2023

Zitat von BlueCoffee

Ive used keepass for years never liked XC https://keepass.info/

Same here, but honestly... It can't hold a candle to Vaultwarden, IMO.

I used KeePass until... probably 3yrs ago, and switched to Vaultwarden. I really like it.

BlueCoffee · 21. Oktober 2023

So ive had ago with vaultwarden and its so anoying with ports. I have many sites like this

10.0.0.222:9483

10.0.0.222:8080

10.0.0.222:1233

10.0.0.222:4556

It seem to think every single 10.0.0.222 is the same and shows me a huge list of logins even tho ive saved the port numbers. Is this normal? Keepass does not do this keep knows the differences of ports.

ashven288 · 23. Oktober 2023

Zitat von BlueCoffee

So ive had ago with vaultwarden and its so anoying with ports. I have many sites like this

10.0.0.222:9483
10.0.0.222:8080
10.0.0.222:1233
10.0.0.222:4556

It seem to think every single 10.0.0.222 is the same and shows me a huge list of logins even tho ive saved the port numbers. Is this normal? Keepass does not do this keep knows the differences of ports.

Alles anzeigen

Change the url match detention from "default match detection" to "host".

Using URIs | Bitwarden Help Center

fbeye · 23. Oktober 2023

Feels like way too much. I just install the BitWarden iPhone app and then the browser extension on my home and work PC.

I ain’t got time for all the nonsense.

opnmdvlat · 26. Oktober 2023

I just switched to OMV and couldn't get it running. It was running before on my old Debian 12 machine,

but I had error messages like this in OMV:

Spoiler anzeigen

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker compose --file '/dockerCompose/Vaultwarden/Vaultwarden.yml' --env-file '/dockerCompose/Vaultwarden/Vaultwarden.env' --env-file '/dockerCompose/global.env' up -d 2>&1':  Network vaultwarden_default  Creating
Network vaultwarden_default  Error
failed to create network vaultwarden_default: Error response from daemon: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-9d12b6082639 -j DOCKER: iptables v1.8.7 (nf_tables): Chain 'DOCKER' does not exist
Try `iptables -h' or 'iptables --help' for more information.
(exit status 2)


or


OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker compose --file '/dockerCompose/Vaultwarden/Vaultwarden.yml' --env-file '/dockerCompose/Vaultwarden/Vaultwarden.env' --env-file '/dockerCompose/global.env' up -d 2>&1':  Network vaultwarden_default  Creating
Network vaultwarden_default  Error
failed to create network vaultwarden_default: Error response from daemon: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-9d12b6082639 -j DOCKER: iptables v1.8.7 (nf_tables): Chain 'DOCKER' does not exist
Try `iptables -h' or 'iptables --help' for more information.
(exit status 2) in /usr/share/openmediavault/engined/rpc/compose.inc:693
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(620): OMVRpcServiceCompose->{closure}('/tmp/bgstatusNL...', '/tmp/bgoutput68...')
#1 /usr/share/openmediavault/engined/rpc/compose.inc(696): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#2 [internal function]: OMVRpcServiceCompose->doCommand(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1)
#6 {main}

Alles anzeigen

Problem was I had a comment in my /etc/openmediavault/config.xml between the <iptables> flag which I guess is already a known problem from 2014 I had from here Re: [Solved] Error... iptables: 7: -A: not found

So if anyone comes around this problem, this might be your solution.

raulfg3 · 26. Oktober 2023

error is: failed to create network vaultwarden_default

Please try to use same network that you use in swag

PD: is recomended to use a new bridge network for all your containers.

I use a bridge network called "my-net" on all my containers

documentation: https://docs.docker.com/network/drivers/bridge/

macom · 26. Oktober 2023

Zitat von opnmdvlat

It was running before on my old Debian 12 machine,

Are you sure? OMV6 runs on Debian 11 (Bullseye).

opnmdvlat · 26. Oktober 2023

Zitat von macom

Are you sure? OMV6 runs on Debian 11 (Bullseye).

Yes! I formatted and reinstalled my machine yesterday. It had (native) Debian 12 before and now OMV 6.

And the error message saying something about vaultwarden_default is saying it like this because it wasn't able to connect to the network where vaultwarden and caddy as my reverse proxy are running in so it creates itself an own network named container_default.

The error was resolved after the iptables entry got fixed and the network is gone.

Anyone use bitwarden in docker?

BlueCoffee 15. Oktober 2023

Jetzt mitmachen!