[GH-ISSUE #2853] 1.26.0-alpine Docker image fails to start #18171

New Issue

Closed

opened 2026-04-25 20:23:26 -05:00 by GiteaMirror · 4 comments

GiteaMirror commented 2026-04-25 20:23:26 -05:00

Owner

Copy Link

Originally created by @jheiselman on GitHub (Oct 21, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2853

Subject of the issue

Image version for vaultwarden/alpine:latest fails to start with error logged "Command not found: /start.sh".

Deployment environment

• vaultwarden version: 1.26.0

• Install method: Docker image vaultwarden/alpine:latest as of 20 October, 2022

• Clients used: NA

• Reverse proxy and version: NA

• MySQL/MariaDB or PostgreSQL version: NA

• Other relevant details:

Steps to reproduce

docker run vaultwarden/alpine:1.26.0

Expected behaviour

Service should startup

Actual behaviour

Service fails to start with error "Command not found: /start.sh"

Troubleshooting data

Reverting to 1.25.2-alpine works properly

Originally created by @jheiselman on GitHub (Oct 21, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2853 ### Subject of the issue Image version for vaultwarden/alpine:latest fails to start with error logged "Command not found: /start.sh". ### Deployment environment * vaultwarden version: 1.26.0 * Install method: Docker image vaultwarden/alpine:latest as of 20 October, 2022 * Clients used: NA * Reverse proxy and version: NA * MySQL/MariaDB or PostgreSQL version: NA * Other relevant details: ### Steps to reproduce docker run vaultwarden/alpine:1.26.0 ### Expected behaviour Service should startup ### Actual behaviour Service fails to start with error "Command not found: /start.sh" ### Troubleshooting data Reverting to 1.25.2-alpine works properly

GiteaMirror closed this issue 2026-04-25 20:23:27 -05:00

GiteaMirror commented 2026-04-25 20:23:28 -05:00

Author

Owner

Copy Link

@jheiselman commented on GitHub (Oct 21, 2022):

For what it's worth, the /start.sh script does appear to be in the image and indeed runs when called directly.

pi@raspberrypi:~/bitwarden $ docker run -it --rm --entrypoint bash vaultwarden/server:alpine
bash-5.1# ls
bin             dev             healthcheck.sh  lib             mnt             proc            run             srv             sys             usr             vaultwarden
data            etc             home            media           opt             root            sbin            start.sh        tmp             var             web-vault
bash-5.1# ls -l
total 39036
drwxr-xr-x    1 root     root          4096 Oct 14  2022 bin
drwxr-xr-x    2 root     root          4096 Oct 14  2022 data
drwxr-xr-x    5 root     root           340 Oct 21  2022 dev
drwxr-xr-x    1 root     root          4096 Oct 21  2022 etc
-rwxr-xr-x    1 root     root          1684 Oct 14  2022 healthcheck.sh
drwxr-xr-x    2 root     root          4096 Jul 18  2022 home
drwxr-xr-x    1 root     root          4096 Aug  5  2022 lib
drwxr-xr-x    5 root     root          4096 Jul 18  2022 media
drwxr-xr-x    2 root     root          4096 Jul 18  2022 mnt
drwxr-xr-x    2 root     root          4096 Jul 18  2022 opt
dr-xr-xr-x  232 root     root             0 Oct 21  2022 proc
drwx------    2 root     root          4096 Jul 18  2022 root
drwxr-xr-x    1 root     root          4096 Aug  5  2022 run
drwxr-xr-x    1 root     root          4096 Aug  5  2022 sbin
drwxr-xr-x    2 root     root          4096 Jul 18  2022 srv
-rwxr-xr-x    1 root     root           696 Oct 14  2022 start.sh
dr-xr-xr-x   12 root     root             0 Oct 21  2022 sys
drwxrwxrwt    2 root     root          4096 Jul 18  2022 tmp
drwxr-xr-x    1 root     root          4096 Aug  5  2022 usr
drwxr-xr-x    1 root     root          4096 Jul 18  2022 var
-rwxr-xr-x    1 root     root      39898984 Oct 14  2022 vaultwarden
drwxr-xr-x    9 root     root          4096 Oct 14  2022 web-vault
bash-5.1# cat start.sh
#!/bin/sh

if [ -r /etc/vaultwarden.sh ]; then
    . /etc/vaultwarden.sh
elif [ -r /etc/bitwarden_rs.sh ]; then
    echo "### You are using the old /etc/bitwarden_rs.sh script, please migrate to /etc/vaultwarden.sh ###"
    . /etc/bitwarden_rs.sh
fi

if [ -d /etc/vaultwarden.d ]; then
    for f in /etc/vaultwarden.d/*.sh; do
        if [ -r "${f}" ]; then
            . "${f}"
        fi
    done
elif [ -d /etc/bitwarden_rs.d ]; then
    echo "### You are using the old /etc/bitwarden_rs.d script directory, please migrate to /etc/vaultwarden.d ###"
    for f in /etc/bitwarden_rs.d/*.sh; do
        if [ -r "${f}" ]; then
            . "${f}"
        fi
    done
fi

exec /vaultwarden "${@}"
bash-5.1# ./start.sh
/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.26.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/

[INFO] No .env file found.

[2022-10-21 18:36:05.839][vaultwarden][ERROR] No persistent volume!
########################################################################################
# It looks like you did not configure a persistent volume!                             #
# This will result in permanent data loss when the container is removed or updated!    #
# If you really want to use volatile storage set `I_REALLY_WANT_VOLATILE_STORAGE=true` #
########################################################################################

bash-5.1#
exit

<!-- gh-comment-id:1287313071 --> @jheiselman commented on GitHub (Oct 21, 2022): For what it's worth, the /start.sh script does appear to be in the image and indeed runs when called directly. ```shell pi@raspberrypi:~/bitwarden $ docker run -it --rm --entrypoint bash vaultwarden/server:alpine bash-5.1# ls bin dev healthcheck.sh lib mnt proc run srv sys usr vaultwarden data etc home media opt root sbin start.sh tmp var web-vault bash-5.1# ls -l total 39036 drwxr-xr-x 1 root root 4096 Oct 14 2022 bin drwxr-xr-x 2 root root 4096 Oct 14 2022 data drwxr-xr-x 5 root root 340 Oct 21 2022 dev drwxr-xr-x 1 root root 4096 Oct 21 2022 etc -rwxr-xr-x 1 root root 1684 Oct 14 2022 healthcheck.sh drwxr-xr-x 2 root root 4096 Jul 18 2022 home drwxr-xr-x 1 root root 4096 Aug 5 2022 lib drwxr-xr-x 5 root root 4096 Jul 18 2022 media drwxr-xr-x 2 root root 4096 Jul 18 2022 mnt drwxr-xr-x 2 root root 4096 Jul 18 2022 opt dr-xr-xr-x 232 root root 0 Oct 21 2022 proc drwx------ 2 root root 4096 Jul 18 2022 root drwxr-xr-x 1 root root 4096 Aug 5 2022 run drwxr-xr-x 1 root root 4096 Aug 5 2022 sbin drwxr-xr-x 2 root root 4096 Jul 18 2022 srv -rwxr-xr-x 1 root root 696 Oct 14 2022 start.sh dr-xr-xr-x 12 root root 0 Oct 21 2022 sys drwxrwxrwt 2 root root 4096 Jul 18 2022 tmp drwxr-xr-x 1 root root 4096 Aug 5 2022 usr drwxr-xr-x 1 root root 4096 Jul 18 2022 var -rwxr-xr-x 1 root root 39898984 Oct 14 2022 vaultwarden drwxr-xr-x 9 root root 4096 Oct 14 2022 web-vault bash-5.1# cat start.sh #!/bin/sh if [ -r /etc/vaultwarden.sh ]; then . /etc/vaultwarden.sh elif [ -r /etc/bitwarden_rs.sh ]; then echo "### You are using the old /etc/bitwarden_rs.sh script, please migrate to /etc/vaultwarden.sh ###" . /etc/bitwarden_rs.sh fi if [ -d /etc/vaultwarden.d ]; then for f in /etc/vaultwarden.d/*.sh; do if [ -r "${f}" ]; then . "${f}" fi done elif [ -d /etc/bitwarden_rs.d ]; then echo "### You are using the old /etc/bitwarden_rs.d script directory, please migrate to /etc/vaultwarden.d ###" for f in /etc/bitwarden_rs.d/*.sh; do if [ -r "${f}" ]; then . "${f}" fi done fi exec /vaultwarden "${@}" bash-5.1# ./start.sh /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.26.0 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] No .env file found. [2022-10-21 18:36:05.839][vaultwarden][ERROR] No persistent volume! ######################################################################################## # It looks like you did not configure a persistent volume! # # This will result in permanent data loss when the container is removed or updated! # # If you really want to use volatile storage set `I_REALLY_WANT_VOLATILE_STORAGE=true` # ######################################################################################## bash-5.1# exit ```

GiteaMirror commented 2026-04-25 20:23:28 -05:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Oct 21, 2022):

See #2656

<!-- gh-comment-id:1287485129 --> @BlackDex commented on GitHub (Oct 21, 2022): See #2656

GiteaMirror commented 2026-04-25 20:23:28 -05:00

Author

Owner

Copy Link

@jheiselman commented on GitHub (Oct 21, 2022):

Okay, so a bind mount is no longer acceptable. That's fine, however, documentation needs to be updated.
https://github.com/dani-garcia/vaultwarden/wiki/Starting-a-Container still guides users to created a bind mount.

Further, the volume check that is mentioned as fixed in 1.25.2 apparently isn't as I am currently running 1.25.2-alpine with a bind mount without issue.

<!-- gh-comment-id:1287495390 --> @jheiselman commented on GitHub (Oct 21, 2022): Okay, so a bind mount is no longer acceptable. That's fine, however, documentation needs to be updated. https://github.com/dani-garcia/vaultwarden/wiki/Starting-a-Container still guides users to created a bind mount. Further, the volume check that is mentioned as fixed in 1.25.2 apparently isn't as I am currently running 1.25.2-alpine with a bind mount without issue.

GiteaMirror commented 2026-04-25 20:23:29 -05:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Oct 21, 2022):

A bind mount is fine, that is what I'm using my self and no need for that env value.

If you can post your docker/docker-compose config, maybe we can help spotting something wrong.

<!-- gh-comment-id:1287497164 --> @BlackDex commented on GitHub (Oct 21, 2022): A bind mount is fine, that is what I'm using my self and no need for that env value. If you can post your docker/docker-compose config, maybe we can help spotting something wrong.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.36.0

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#18171