starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00

[GH-ISSUE #4120] Thread panick with new version of vaultwarden on older distribution. #1789

New issue

Closed

opened 2026-03-03 02:12:12 +03:00 by kerem · 7 comments

kerem commented

2026-03-03 02:12:12 +03:00

Owner

Originally created by @Callixte-de-Vulpillieres on GitHub (Dec 1, 2023).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4120

Subject of the issue

The new version of vaultwarden does a thread panick when launched on my Synology NAS from 2016.

Deployment environment

vaultwarden version: 1.30.1

Install method: Pre-built binary extracted from the docker images
System : Linux 3.10.108 , armv7l GNU/Linux synology_armada38x_ds216j

Steps to reproduce

I used my usual setup with few custom variables, set inside the .env file.
Starting the app with systemctl or just from the shell lead to an immediate crash

Actual behaviour

It crashes immediatly when trying to start it

Troubleshooting data

thread 'main' panicked at library/std/src/sys/unix/time.rs:420:72:
called `Result::unwrap()` on an `Err` value: Os { code: 22, kind: InvalidInput, message: "Invalid argument" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Adding 'trace' logs and setting RUST_BACKTRACE=1 didn't give any info.

I know my setup is unusual, with an old version of the kernel. But if you have any idea for a workaround, it would be great.
Thanks for this great project !

Originally created by @Callixte-de-Vulpillieres on GitHub (Dec 1, 2023). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4120   ### Subject of the issue  The new version of vaultwarden does a thread panick when launched on my Synology NAS from 2016. ### Deployment environment     * vaultwarden version: 1.30.1  * Install method: Pre-built binary extracted from the docker images * System : Linux 3.10.108 , armv7l GNU/Linux synology_armada38x_ds216j ### Steps to reproduce  I used my usual setup with few custom variables, set inside the .env file. Starting the app with systemctl or just from the shell lead to an immediate crash ### Actual behaviour  It crashes immediatly when trying to start it ### Troubleshooting data  ``` thread 'main' panicked at library/std/src/sys/unix/time.rs:420:72: called `Result::unwrap()` on an `Err` value: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` Adding 'trace' logs and setting `RUST_BACKTRACE=1` didn't give any info. I know my setup is unusual, with an old version of the kernel. But if you have any idea for a workaround, it would be great. Thanks for this great project !

kerem closed this issue

2026-03-03 02:12:12 +03:00

kerem commented

2026-03-03 02:12:13 +03:00

Author

Owner

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

Your Linux Host is to old. Check if there are updates available for your NAS which might help.

Else i suggest to try to use the -alpine tagged versions like latest-alpine or 1.30.1-alpine, those will probably work, but not sure.

@BlackDex commented on GitHub (Dec 1, 2023): Your Linux Host is to old. Check if there are updates available for your NAS which might help. Else i suggest to try to use the `-alpine` tagged versions like `latest-alpine` or `1.30.1-alpine`, those will probably work, but not sure.

kerem commented

2026-03-03 02:12:13 +03:00

Author

Owner

@Callixte-de-Vulpillieres commented on GitHub (Dec 1, 2023):

Thanks for your quick answer. No, my NAS is up-to-date, but for some reason Synology has decided to keep using this old version of the kernel.
I'm already using the alpine version.

@Callixte-de-Vulpillieres commented on GitHub (Dec 1, 2023): Thanks for your quick answer. No, my NAS is up-to-date, but for some reason Synology has decided to keep using this old version of the kernel. I'm already using the alpine version.

kerem commented

2026-03-03 02:12:13 +03:00

Author

Owner

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

Then your Docker platform is probably out-of-date also i think. It needs at least v20.10 if I'm correct.
Check if you can do the following on your NAS:
https://github.com/dani-garcia/vaultwarden/issues/2497#issuecomment-1136988758

Edit: Also see: github.com/rust-lang/rust@cc66ad4689/library/std/src/sys/unix/fs.rs (L185-L194)

@BlackDex commented on GitHub (Dec 1, 2023): Then your Docker platform is probably out-of-date also i think. It needs at least v20.10 if I'm correct. Check if you can do the following on your NAS: https://github.com/dani-garcia/vaultwarden/issues/2497#issuecomment-1136988758 Edit: Also see: https://github.com/rust-lang/rust/blob/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys/unix/fs.rs#L185-L194

kerem commented

2026-03-03 02:12:13 +03:00

Author

Owner

@Callixte-de-Vulpillieres commented on GitHub (Dec 1, 2023):

My NAS doesn't support docker, so I'm using pre-built binaries extracted from the docker image, following this page of the wiki. Thus, I can't use the --security-opt seccomp=unconfined.
For the other link, I'm not sure what to do with this info.

@Callixte-de-Vulpillieres commented on GitHub (Dec 1, 2023): My NAS doesn't support docker, so I'm using pre-built binaries extracted from the docker image, following [this page of the wiki](https://github.com/dani-garcia/vaultwarden/wiki/Pre-built-binaries). Thus, I can't use the `--security-opt seccomp=unconfined`. For the other link, I'm not sure what to do with this info.

kerem commented

2026-03-03 02:12:13 +03:00

Author

Owner

@BlackDex commented on GitHub (Dec 4, 2023):

You could try to use the armv6 version maybe?
It could be that some features are not supported by the CPU of your NAS which are now used in some way.
Using the armv6 binary should just work fine on an armv7 CPU.

@BlackDex commented on GitHub (Dec 4, 2023): You could try to use the armv6 version maybe? It could be that some features are not supported by the CPU of your NAS which are now used in some way. Using the armv6 binary should just work fine on an armv7 CPU.

kerem commented

2026-03-03 02:12:13 +03:00

Author

Owner

@Callixte-de-Vulpillieres commented on GitHub (Dec 4, 2023):

Thanks a lot for the help, it works perfectly with armv6 !

@Callixte-de-Vulpillieres commented on GitHub (Dec 4, 2023): Thanks a lot for the help, it works perfectly with armv6 !

kerem commented

2026-03-03 02:12:13 +03:00

Author

Owner

@BlackDex commented on GitHub (Dec 4, 2023):

Nice, glad that worked :).

@BlackDex commented on GitHub (Dec 4, 2023): Nice, glad that worked :).

kerem referenced this issue

2026-03-03 09:09:19 +03:00

[PR #1789] [CLOSED] Only create private key in pem format if it doesn't already exist #3005