Latest docker version (as of 2023-09-01) fails to spawn worker #1459

Closed
opened 2026-04-06 01:54:36 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @phormix on 9/6/2023

Subject of the issue

Docker version (1.29.2: latest, pulled from 2023-09-01) fails. Logs indicate an issue spawning worker threads per error (continual)

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

Deployment environment

Debian Bookworm with kernel 6.1.0-11-amd64

  • vaultwarden version: 1.29.2
  • Install method: Docker image

  • Clients used: Web vault, Android

  • Reverse proxy and version: Apache 2.4.57/debian

  • MySQL/MariaDB or PostgreSQL version: N/A (in docker image)

  • Other relevant details:

Steps to reproduce

docker container start vaultwarden

Expected behaviour

container normal startup

Actual behaviour

Thread failed due to error

Troubleshooting data

This error is repeated in the logs (per "docker logs vaultwarden")

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
*Originally created by @phormix on 9/6/2023* <!-- # ### 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 Docker version (1.29.2: latest, pulled from 2023-09-01) fails. Logs indicate an issue spawning worker threads per error (continual) 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 ### Deployment environment Debian Bookworm with kernel 6.1.0-11-amd64 <!-- ========================================================================================= 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: Web vault, Android * Reverse proxy and version: Apache 2.4.57/debian * MySQL/MariaDB or PostgreSQL version: N/A (in docker image) * Other relevant details: ### Steps to reproduce docker container start vaultwarden ### Expected behaviour container normal startup ### Actual behaviour Thread failed due to error ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> This error is repeated in the logs (per "docker logs vaultwarden") ``` 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 ```
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#1459