Vaultwarden docker 1.29.2 won't start #1475

New Issue

MrUnknownDE · 2026-04-06T01:55:58+02:00

MrUnknownDE commented

2026-04-06 01:55:58 +02:00

Originally created by @daevidt on 9/1/2023

Subject of the issue

Vaultwarden 1.29.2 (docker) won't start after upgrade (docker image update).

Deployment environment

os version: Ubuntu 22.04.3 LTS
vaultwarden version: 1.29.2 (could not start)
Install method: docker image (latest)
Clients used: web vault, Android
Reverse proxy and version: Apache 2.4.52-1ubuntu4.6
MySQL/MariaDB or PostgreSQL version: N. A. (sqlite3)
Other relevant details:

Only accessible from an internal network (restricted in Apache and firewall)
.env file settings:
WEB_VAULT_ENABLED=false
SIGNUPS_ALLOWED=false
DOMAIN=https://...
USE_SENDMAIL=true

Steps to reproduce

$ docker stop vaultwarden
$ docker rm vaultwarden
$ docker pull vaultwarden/server:latest
$ docker run -d --restart unless-stopped --name vaultwarden -e bwrs.env -v /opt/bitwarden/bwrsdata:/data/ -p 449:80 vaultwarden/server:latest

Expected behaviour

the docker container should start

Actual behaviour

the docker container stuck in a restart loop

Troubleshooting data

$ docker logs vaultwarden

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
thread 'main' panicked at 'OS can't spawn worker thread: Operation not permitted (os error 1)', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.31.0/src/runtime/scheduler/multi_thread/worker.rs:447:13

I tried to set RUST_BACKTRACE=1 in bwrs.env, but it made no difference..

*Originally created by @daevidt on 9/1/2023* ### Subject of the issue Vaultwarden 1.29.2 (docker) won't start after upgrade (docker image update). ### Deployment environment * os version: Ubuntu 22.04.3 LTS * vaultwarden version: 1.29.2 (could not start) * Install method: docker image (latest) * Clients used: web vault, Android * Reverse proxy and version: Apache 2.4.52-1ubuntu4.6 * MySQL/MariaDB or PostgreSQL version: N. A. (sqlite3) * Other relevant details: Only accessible from an internal network (restricted in Apache and firewall) .env file settings: WEB_VAULT_ENABLED=false SIGNUPS_ALLOWED=false DOMAIN=https://... USE_SENDMAIL=true ### Steps to reproduce $ docker stop vaultwarden $ docker rm vaultwarden $ docker pull vaultwarden/server:latest $ docker run -d --restart unless-stopped --name vaultwarden -e bwrs.env -v /opt/bitwarden/bwrsdata:/data/ -p 449:80 vaultwarden/server:latest ### Expected behaviour the docker container should start ### Actual behaviour the docker container stuck in a restart loop ### Troubleshooting data $ docker logs vaultwarden note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace thread 'main' panicked at 'OS can't spawn worker thread: Operation not permitted (os error 1)', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.31.0/src/runtime/scheduler/multi_thread/worker.rs:447:13 I tried to set RUST_BACKTRACE=1 in bwrs.env, but it made no difference..

MrUnknownDE closed this issue

2026-04-06 01:55:58 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1475