bookworm image fails to start without privileged mode #1468

New Issue

MrUnknownDE · 2026-04-06T01:54:37+02:00

MrUnknownDE commented

2026-04-06 01:54:37 +02:00

Originally created by @bjo81 on 9/4/2023

Subject of the issue

After uprading from 1.29.1 to 1.29.2 the image does not start.

Deployment environment

Clients used: Web, Desktop
Reverse proxy and version: nginx
MySQL/MariaDB or PostgreSQL version: MySQL
The issue does not appear with the alpine image

Steps to reproduce

Uprade from 1.29.1 to 1.29.2

Expected behaviour

The container starts.

Actual behaviour

The container does not start except "privileged: true" is set in the docker-compose file. Maybe it's the same issue as #3839 ?

Troubleshooting data

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
stack backtrace:
   0:     0x5635a9c71ca3 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hbd7d55b7108d2ab8
   1:     0x5635a96ca3df - core::fmt::write::h6d54cd7c9e155ec5
   2:     0x5635a9c6e8d7 - std::io::Write::write_fmt::h6a453a71c692f63b
   3:     0x5635a9c71a75 - std::sys_common::backtrace::print::h4ddf81241a51b337
   4:     0x5635a9c734b0 - std::panicking::default_hook::{{closure}}::hff91f1f484ade5cd
   5:     0x5635a9c73274 - std::panicking::default_hook::h21f14afd59f7aef9
   6:     0x5635a9c73999 - std::panicking::rust_panic_with_hook::h45f66047b14c555c
   7:     0x5635a9c738a4 - std::panicking::begin_panic_handler::{{closure}}::h49d1a88ef0908eb4
   8:     0x5635a9c72096 - std::sys_common::backtrace::__rust_end_short_backtrace::hccebf9e57f8cc425
   9:     0x5635a9c73642 - rust_begin_unwind
  10:     0x5635a961d883 - core::panicking::panic_fmt::h54ec9d0e3180a83d
  11:     0x5635a9cac9f4 - tokio::runtime::blocking::pool::Spawner::spawn_blocking::h9e0ded7b77863876
  12:     0x5635a9cabd05 - tokio::runtime::blocking::pool::spawn_blocking::hb15e5178f17f818b
  13:     0x5635a9cc066b - tokio::runtime::scheduler::multi_thread::worker::Launch::launch::h6ce2d7d02be3860d
  14:     0x5635a9cd33f9 - tokio::runtime::builder::Builder::build::h6fb748647923ea1f
  15:     0x5635aa0ca52e - vaultwarden::main::h222f937f9ca88bfc
  16:     0x5635aa4c11d7 - std::sys_common::backtrace::__rust_begin_short_backtrace::h267d3b5af2cab27a
  17:     0x5635aa01bc38 - std::rt::lang_start::{{closure}}::h3ae0294076e6f9bb
  18:     0x5635a9c66f15 - std::rt::lang_start_internal::hf502095b101390bb
  19:     0x5635aa0ca895 - main
  20:     0x7fee074051ca - <unknown>
  21:     0x7fee07405285 - __libc_start_main
  22:     0x5635a96612b1 - _start
  23:                0x0 - <unknown>

*Originally created by @bjo81 on 9/4/2023* ### Subject of the issue After uprading from 1.29.1 to 1.29.2 the image does not start. ### Deployment environment * Clients used: Web, Desktop * Reverse proxy and version: nginx * MySQL/MariaDB or PostgreSQL version: MySQL * The issue does not appear with the alpine image ### Steps to reproduce Uprade from 1.29.1 to 1.29.2 ### Expected behaviour The container starts. ### Actual behaviour The container does not start except "privileged: true" is set in the docker-compose file. Maybe it's the same issue as #3839 ? ### Troubleshooting data ``` 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 stack backtrace: 0: 0x5635a9c71ca3 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hbd7d55b7108d2ab8 1: 0x5635a96ca3df - core::fmt::write::h6d54cd7c9e155ec5 2: 0x5635a9c6e8d7 - std::io::Write::write_fmt::h6a453a71c692f63b 3: 0x5635a9c71a75 - std::sys_common::backtrace::print::h4ddf81241a51b337 4: 0x5635a9c734b0 - std::panicking::default_hook::{{closure}}::hff91f1f484ade5cd 5: 0x5635a9c73274 - std::panicking::default_hook::h21f14afd59f7aef9 6: 0x5635a9c73999 - std::panicking::rust_panic_with_hook::h45f66047b14c555c 7: 0x5635a9c738a4 - std::panicking::begin_panic_handler::{{closure}}::h49d1a88ef0908eb4 8: 0x5635a9c72096 - std::sys_common::backtrace::__rust_end_short_backtrace::hccebf9e57f8cc425 9: 0x5635a9c73642 - rust_begin_unwind 10: 0x5635a961d883 - core::panicking::panic_fmt::h54ec9d0e3180a83d 11: 0x5635a9cac9f4 - tokio::runtime::blocking::pool::Spawner::spawn_blocking::h9e0ded7b77863876 12: 0x5635a9cabd05 - tokio::runtime::blocking::pool::spawn_blocking::hb15e5178f17f818b 13: 0x5635a9cc066b - tokio::runtime::scheduler::multi_thread::worker::Launch::launch::h6ce2d7d02be3860d 14: 0x5635a9cd33f9 - tokio::runtime::builder::Builder::build::h6fb748647923ea1f 15: 0x5635aa0ca52e - vaultwarden::main::h222f937f9ca88bfc 16: 0x5635aa4c11d7 - std::sys_common::backtrace::__rust_begin_short_backtrace::h267d3b5af2cab27a 17: 0x5635aa01bc38 - std::rt::lang_start::{{closure}}::h3ae0294076e6f9bb 18: 0x5635a9c66f15 - std::rt::lang_start_internal::hf502095b101390bb 19: 0x5635aa0ca895 - main 20: 0x7fee074051ca - <unknown> 21: 0x7fee07405285 - __libc_start_main 22: 0x5635a96612b1 - _start 23: 0x0 - <unknown> ```

MrUnknownDE closed this issue

2026-04-06 01:54:37 +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#1468