Startup errors using new image on raspberry pi #905

Closed
opened 2025-10-09 16:56:33 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @drduker on GitHub.

Had to update to latest image since the client wasn't working with my setup. I haven't used my instance in probably a year due to moving around.

I have a rapsberry pi 4 running rasbian buster.

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

Anyone know a way to workaroudn this to fix?

Subject of the issue

Deployment environment

  • vaultwarden version:
  • Install method:

  • Clients used:

  • Reverse proxy and version:

  • MySQL/MariaDB or PostgreSQL version:

  • Other relevant details:

Steps to reproduce

Expected behaviour

Actual behaviour

Troubleshooting data

Originally created by @drduker on GitHub. <!-- # ### 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 # ### --> Had to update to latest image since the client wasn't working with my setup. I haven't used my instance in probably a year due to moving around. I have a rapsberry pi 4 running rasbian buster. "Operation not permitted" }', library/std/src/sys/unix/time.rs:350:72 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }', library/std/src/sys/unix/time.rs:350:72 Anyone know a way to workaroudn this to fix? <!-- 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. --> ### 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: <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> * Reverse proxy and version: <!-- if applicable --> * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> ### Expected behaviour <!-- Tell us what you expected to happen --> ### Actual behaviour <!-- Tell us what actually happened --> ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
Author
Owner

@dani-garcia commented on GitHub:

Sounds like it could be this issue? https://github.com/dani-garcia/vaultwarden/issues/2497

Either using alpine or --security-opt seccomp=unconfined solves the problem

@dani-garcia commented on GitHub: Sounds like it could be this issue? https://github.com/dani-garcia/vaultwarden/issues/2497 Either using alpine or `--security-opt seccomp=unconfined` solves the problem
Author
Owner

@BlackDex commented on GitHub:

Which version are you running? And which version of your host os are you running?

I suggest to use the Alpine image instead if your host os is not the latest stable version.

@BlackDex commented on GitHub: Which version are you running? And which version of your host os are you running? I suggest to use the Alpine image instead if your host os is not the latest stable version.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#905