Docker start fails with latest image version #3340

New Issue

MrUnknownDE · 2026-04-06T04:42:31+02:00

MrUnknownDE commented

2026-04-06 04:42:31 +02:00

Originally created by @dominikstraessle on 9/6/2019

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:alpine
Working: bitwardenrs/server:1.10.0-alpine

A docker inspect of the container gives the following error message in the Health section:

{
"Health": {
                "Status": "unhealthy",
                "FailingStreak": 3,
                "Log": [
                    {
                        "Start": "2019-09-06T08:29:51.743115269+02:00",
                        "End": "2019-09-06T08:29:52.162213371+02:00",
                        "ExitCode": 1,
                        "Output": "/bin/sh: bash: not found\n"
                    },
                    {
                        "Start": "2019-09-06T08:30:02.181111963+02:00",
                        "End": "2019-09-06T08:30:02.562809027+02:00",
                        "ExitCode": 1,
                        "Output": "/bin/sh: bash: not found\n"
                    },
                    {
                        "Start": "2019-09-06T08:30:12.590872269+02:00",
                        "End": "2019-09-06T08:30:12.964838957+02:00",
                        "ExitCode": 1,
                        "Output": "/bin/sh: bash: not found\n"
                    }
                ]
            }
}

A docker stack ps <my-bitwarden-service-name> gives the following ERROR:

task: non-zero exit (137)

I think this could have something to do with the following merge request: Adds Healthcheck for default docker container #589

*Originally created by @dominikstraessle on 9/6/2019* 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:alpine` Working: `bitwardenrs/server:1.10.0-alpine` A docker inspect of the container gives the following error message in the `Health` section: ```json { "Health": { "Status": "unhealthy", "FailingStreak": 3, "Log": [ { "Start": "2019-09-06T08:29:51.743115269+02:00", "End": "2019-09-06T08:29:52.162213371+02:00", "ExitCode": 1, "Output": "/bin/sh: bash: not found\n" }, { "Start": "2019-09-06T08:30:02.181111963+02:00", "End": "2019-09-06T08:30:02.562809027+02:00", "ExitCode": 1, "Output": "/bin/sh: bash: not found\n" }, { "Start": "2019-09-06T08:30:12.590872269+02:00", "End": "2019-09-06T08:30:12.964838957+02:00", "ExitCode": 1, "Output": "/bin/sh: bash: not found\n" } ] } } ``` A `docker stack ps <my-bitwarden-service-name>` gives the following ERROR: ``` task: non-zero exit (137) ``` I think this could have something to do with the following merge request: [ Adds Healthcheck for default docker container #589 ](https://github.com/dani-garcia/bitwarden_rs/pull/589)

MrUnknownDE closed this issue

2026-04-06 04:42:31 +02:00

Sign in to join this conversation.

No Label bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#3340