mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #603] Docker start fails with latest image version #400
Labels
No 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
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#400
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @dominikstraessle on GitHub (Sep 6, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/603
I'm running bitwarden_rs with docker in swarm mode and with automatic image updates. Tonight the newest image of bitwarden_rs has been pulled and since then the startup of the container fails. When I afterwards manually pulled the next older version for testing purposes, everything runs smoothly like before.
Not working:
bitwardenrs/server:alpineWorking:
bitwardenrs/server:1.10.0-alpineA docker inspect of the container gives the following error message in the
Healthsection:A
docker stack ps <my-bitwarden-service-name>gives the following ERROR:I think this could have something to do with the following merge request: Adds Healthcheck for default docker container #589
@thehawkes commented on GitHub (Sep 6, 2019):
Same problem here with the latest debian build
the problem in the debian version is that curl is missing in the image that is needed for the healthcheck
i've temp fixed it by installing curl after the container was created
looks like in alpine
bashis missingshould temp fix it. or edit the healthcheck script to use
ash@mprasil commented on GitHub (Sep 6, 2019):
This was caused by #589, as a quick workaround you can add
--no-healthcheckto your docker run command. For docker compose you can disable healthcheck:@mprasil commented on GitHub (Sep 6, 2019):
PR submitted to fix this.
@mprasil commented on GitHub (Sep 6, 2019):
The PR is now merged, it will take couple hours to rebuild all images.