# \[SOLVED\] Dockerless install panicked threads

**URL:** <https://vaultwarden.discourse.group/t/solved-dockerless-install-panicked-threads/1292>\
**Category:** Help\
**Created:** [November 30, 2021, 6:16pm UTC](https://vaultwarden.discourse.group/t/solved-dockerless-install-panicked-threads/1292 "2021-11-30T18:16:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MaxW7](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@MaxW7](https://vaultwarden.discourse.group/u/MaxW7)\
**Post date:** [November 30, 2021, 6:16pm UTC](https://vaultwarden.discourse.group/t/solved-dockerless-install-panicked-threads/1292/1 "2021-11-30T18:16:31Z")

</div>

Hi all,

I am trying to get the [archlinux vaultwarden package](https://archlinux.org/packages/community/x86_64/vaultwarden/) installed inside of a LXC container. Since LXC and Docker use the same method of virtualization, Docker can not run in an unprivileged LXC.

I have been playing with this package and the `/etc/vaultwarden.env` file, but no matter how I try to start it it seems to exit violently with a panicked thread. The error I can extract from `journalctl` is as follows:

```auto
/--------------------------------------------------------------------\
| Starting Vaultwarden |
| Version 1.23.0 |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the |
| official channels to report bugs/features, regardless of client. |
| Send usage/configuration questions or feature requests to: |
| https://vaultwarden.discourse.group/ |
| Report suspected bugs/issues in the software itself at: |
| https://github.com/dani-garcia/vaultwarden/issues/new |
\--------------------------------------------------------------------/
[2021-11-29 19:49:02.077][start][INFO] Rocket has launched from http://0.0.0.0:8000
[2021-11-29 19:49:02.157][panic][ERROR] thread 'unnamed' panicked at 'failed to spawn thread: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }': /rustc/dfc5add915e8bf4accbb7cf4de00351a7c6126a1/library/std/src/thread/mod.rs:630
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: start_thread
  14: __GI___ clone
[2021-11-29 19:49:02.157][panic][ERROR] thread 'main' panicked at 'internal error: entered unreachable code: the call to `handle_threads` should block on success': /build/.cargo/git/checkouts/rocket-8bf16d9ca7e90bdc/263e39b/core/lib/src/rocket.rs:751
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: __libc_start_main
  13: <unknown>
```

The container runs on a Linux 5.10.82-1-lts kernel.

I have not been able to find any other posts regarding this error, and I am not well versed with rust at all and have no clue how to manually debug this problem.

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [November 30, 2021, 6:30pm UTC](https://vaultwarden.discourse.group/t/solved-dockerless-install-panicked-threads/1292/2 "2021-11-30T18:30:04Z")

</div>

You possibly hit this issue [Setup as a systemd service · dani-garcia/vaultwarden Wiki · GitHub](https://github.com/dani-garcia/vaultwarden/wiki/Setup-as-a-systemd-service#service-fails-to-start)

---

<div class="post-metadata">

**Author:** ![MaxW7](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@MaxW7](https://vaultwarden.discourse.group/u/MaxW7)\
**Post date:** [November 30, 2021, 8:10pm UTC](https://vaultwarden.discourse.group/t/solved-dockerless-install-panicked-threads/1292/3 "2021-11-30T20:10:47Z")

</div>

Good shot, this error seems to indeed come from the `LimitNPROC=64` setting in the systemctl unit. Stupid of me that I didn’t find it earlier, but maybe we’ll help someone else in the future with trying to find out the error `:)`