github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-05-24 09:03:15 -05:00
Code Issues 307 Packages Projects Releases 83 Wiki Activity

[GH-ISSUE #3830] Vaultwarden does not start inside docker container #18454

New Issue
Closed
opened 2026-04-25 20:37:31 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-25 20:37:31 -05:00
Owner
Copy Link

Originally created by @PhoenixKarton on GitHub (Sep 1, 2023).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3830

Subject of the issue

Vaultwarden does not start inside docker container

Deployment environment

  • vaultwarden version: 1.29.2

  • Install method: Docker image

  • Clients used: all

  • Reverse proxy and version: caddy v2.7.4

Steps to reproduce

Newest Version (1.29.2) of docker image won't start. Logs return this:

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
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

After downgrading to Version 1.29.1 everything worked fine.

Expected behaviour

Docker container working

Actual behaviour

Docker container not working

Troubleshooting data

Originally created by @PhoenixKarton on GitHub (Sep 1, 2023). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3830 <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> Vaultwarden does not start inside docker container ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.29.2 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker image * Clients used: all * Reverse proxy and version: caddy v2.7.4 ### Steps to reproduce Newest Version (1.29.2) of docker image won't start. Logs return this: ``` 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 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` After downgrading to Version 1.29.1 everything worked fine. ### Expected behaviour Docker container working ### Actual behaviour Docker container not working ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
GiteaMirror commented 2026-04-25 20:37:32 -05:00
Author
Owner
Copy Link

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

Duplicate of #3827

<!-- gh-comment-id:1703101139 --> @BlackDex commented on GitHub (Sep 1, 2023): Duplicate of #3827
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#18454
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?