事情是这样的,一直使用 bitwarden 自建服务[ docker mprasil/bitwarden:latest
] 今天突然发现 edge 的客户端无法登陆了,看了下 好像是 bitwarden 发布了数据不兼容老 server 的更新https://help.ppgg.in/home 然后去 bitwarden docker 搜索了下..最后翻到了 https://bitwarden.com/help/install-on-premise-manual/ ... 看了下 docker-copmpose..惊呆了..真全家桶...
# # 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
![]() | 1 jack778 2023-01-12 00:36:23 +08:00 我也是最近更新了浏览器插件,发现不兼容老的自建服务,一直报密码错误. |
2 0o0O0o0O0o 2023-01-12 00:39:36 +08:00 via iPhone ![]() 我感觉你的 bitwarden 的 api server 用着 star 数为 1 的 fork ,并且四五年不更新,这个事实才更让我吃惊… |
3 molika OP |
4 0o0O0o0O0o 2023-01-12 00:44:44 +08:00 via iPhone @0o0O0o0O0o #2 不过根据 bitwarden 的设计,只要不用 web ,这样也没有什么泄漏密码的风险就是了。就是觉得很惊讶… |
6 0o0O0o0O0o 2023-01-12 00:46:39 +08:00 via iPhone ![]() @molika #3 我是一有更新邮件就去看看 issues ,没有什么 bug 反馈就迫不及待更新,缺点就是容易当小白鼠,哈哈 |
7 knives 2023-01-12 02:53:43 +08:00 话说,自建 bitwarden 用 vaultwarden 这个第三方开源实现更多些吧?这个就没有楼主吐槽的问题了…… |
![]() | 8 msg7086 2023-01-12 02:56:09 +08:00 用着 vaultwarden ,内存就吃了 100M 上下,负载几乎为 0 。 |
12 FundyLiu 2023-01-12 09:05:31 +08:00 vaultwarden 香些 |
![]() | 13 itechify PRO op 用的镜像以前也用过,老是有问题,插入数据可以,更新数据老是提示出错,需要重启服务才行。后来切 vaultwarden ,一切正常了 |
14 klgd 2023-01-12 09:44:39 +08:00 看了一下 我用的是 vaultwarden |
15 Huelse 2023-01-12 09:49:39 +08:00 vaultwarden 好啊,升级也方便,备份下数据直接就可以升级了 |
16 455c4l811WjPy37n 2023-01-12 09:55:50 +08:00 vaultwarden 镜像自建服务, 配合 官方各种 app 和浏览器插件 |
![]() | 17 bluedawn 2023-01-12 11:04:10 +08:00 via iPhone 还是推荐 vaultwarden ,自己用其实没必要用官方那么重的 server 端 |
![]() | 21 Kroos 2023-01-12 11:41:06 +08:00 老哥,我看了一下你以前用的镜像,是第三方开源的版本,用 Rust 写的,不是官方的,你列举的这个全家桶是官方的镜像,建议切换到 Vaultwarden ,你可以去 DockerHub 搜一下你原来的镜像,迁移到了 vaultwarden/server |
22 ciki 2023-01-12 11:43:40 +08:00 一开始就直接用的 vaultwarden |
![]() | 24 Neur2n 2023-01-12 12:46:12 +08:00 也在用 bitwarden ,不熟悉这些技术栈,OP 可以简单说下是什么问题吗?谢谢 |
![]() | 25 blankmiss 2023-01-12 19:57:00 +08:00 https://dnslin.com/archives/62.html 可以看看我这个 哈哈 写的比较简单 |
![]() | 28 linuslv 2023-01-22 16:38:16 +08:00 怪不得我今天看我浏览器插件一直登录不上去说密码错误。。。 |
![]() | 29 linuslv 2023-01-22 16:39:04 +08:00 但我记得我也用的是 vaultwarden 啊。。。。 |
![]() | 30 EchoYang7 2023-02-05 15:30:45 +08:00 @linuslv #28 我也是 我看 docker 镜像也最新的,mac 客户端、手机客户端、网页版都可以进入,只有插件不行。。POST /identity/connect/token (login) => 400 Bad Request |
![]() | 31 frankilla 2024-03-18 01:35:38 +08:00 via iPhone 看不懂,我用 bitwarden ,但是吧 vaultwarden 的 github 页面满屏幕的英语让我看吐了。_(`」 ∠)_ |