github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-09 04:32:44 -05:00
Code Issues 79 Packages Projects Releases 78 Wiki Activity

Vaultwarden docker 1.29.2 won't start #5320

New Issue
Closed
opened 2026-03-07 20:19:36 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-07 20:19:36 -06:00
Owner
Copy Link

Originally created by @daevidt on GitHub (Sep 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 GitHub (Sep 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..
GiteaMirror commented 2026-03-07 20:19:37 -06:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Sep 1, 2023):

Please provide a docker info output, i suspect you are running an older version of Docker which has some issues with newer container images.

@BlackDex commented on GitHub (Sep 1, 2023): Please provide a `docker info` output, i suspect you are running an older version of Docker which has some issues with newer container images.
GiteaMirror commented 2026-03-07 20:19:37 -06:00
Author
Owner
Copy Link

@grantcodes commented on GitHub (Sep 1, 2023):

Just confirming I ran into the same issue and reinstalling / upgrading docker following the official docs seems to have got Vaultwarden up and running for me again.

@grantcodes commented on GitHub (Sep 1, 2023): Just confirming I ran into the same issue and reinstalling / upgrading docker [following the official docs](https://docs.docker.com/) seems to have got Vaultwarden up and running for me again.
GiteaMirror commented 2026-03-07 20:19:37 -06:00
Author
Owner
Copy Link

@jrkoiter commented on GitHub (Sep 1, 2023):

Same issue here. Rolled back to 1.29.1 for now, that works.

@jrkoiter commented on GitHub (Sep 1, 2023): Same issue here. Rolled back to 1.29.1 for now, that works.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#5320
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?