starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-27 07:58:30 +03:00
Code Issues 32 Packages Projects Releases 12 Wiki Activity

Latest Docker build appears "unhealthy" #404

New Issue
Closed
opened 2026-02-04 20:20:36 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 20:20:36 +03:00
Owner
Copy Link

Originally created by @hg2s on GitHub (Sep 6, 2019).

When I try to run the latest build of bitwardenrs/server (amd64, linux) I receive an "unhealthy" status from Docker, like so:

  CONTAINER ID        IMAGE                       COMMAND                  CREATED             STATUS                     PORTS                            NAMES
467d269eebd2        bitwardenrs/server:latest   "./bitwarden_rs"         2 minutes ago       Up 2 minutes (unhealthy)   3012/tcp, 0.0.0.0:8008->80/tcp   bitwarden

If I revert and specify the image 1.10.0 I receive no such message.

The server appears to be working and I have not seen this message before. Is it a problem in my installation, a bug, an artifact? For the moment I am reverting to 1.10.0 specifically.

Ubuntu 18.04.3 LTS | Nginx 1.14.0 | Docker 18.09.5

Thanks for your help.

Originally created by @hg2s on GitHub (Sep 6, 2019). When I try to run the latest build of bitwardenrs/server (amd64, linux) I receive an "unhealthy" status from Docker, like so: ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 467d269eebd2 bitwardenrs/server:latest "./bitwarden_rs" 2 minutes ago Up 2 minutes (unhealthy) 3012/tcp, 0.0.0.0:8008->80/tcp bitwarden ``` If I revert and specify the image 1.10.0 I receive no such message. The server appears to be working and I have not seen this message before. Is it a problem in my installation, a bug, an artifact? For the moment I am reverting to 1.10.0 specifically. Ubuntu 18.04.3 LTS | Nginx 1.14.0 | Docker 18.09.5 Thanks for your help.
OVERLORD commented 2026-02-04 20:20:46 +03:00
Author
Owner
Copy Link

@hg2s commented on GitHub (Sep 6, 2019):

I see a new release of bitwardenrs/server, Digest 7e5ba76c8154, that seems to be working. The container spins up with a "healthy" status. -Thanks!

@hg2s commented on GitHub (Sep 6, 2019): I see a new release of bitwardenrs/server, Digest 7e5ba76c8154, that seems to be working. The container spins up with a "healthy" status. -Thanks!
OVERLORD commented 2026-02-04 20:20:48 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Sep 6, 2019):

Yep there was a bug in the new health check code but it's fixed now. Note that it was reporting false positives, so everything should have worked anyway.

@dani-garcia commented on GitHub (Sep 6, 2019): Yep there was a bug in the new health check code but it's fixed now. Note that it was reporting false positives, so everything should have worked anyway.
OVERLORD commented 2026-02-04 20:20:55 +03:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Sep 6, 2019):

Latest images should be fine now, apologies for the inconveniences caused.

@mprasil commented on GitHub (Sep 6, 2019): Latest images should be fine now, apologies for the inconveniences caused.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#404
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?