Repository: dani-garcia/vaultwarden

Issue #2497: cannot start docker container v1.25.0
Created: 2022-05-24T21:25:16Z
Subject of the issue

When I try to start my docker container it does not start.
Deployment environment





vaultwarden version: 1.25.0




Install method: Docker


Other relevant details:


Steps to reproduce

Starting the container via:
docker run -d --name vaultwarden \
  -e ROCKET_TLS='{certs="/ssl/live/<domain>/fullchain.pem",key="/ssl/live/<domain>/privkey.pem"}' \
  -e SIGNUPS_ALLOWED=false \
  -e ADMIN_TOKEN=<token string> \
  -v /etc/letsencrypt/:/ssl/ \
  -v /home/<user>/programme/vaultwarden/vw-data/:/data/ \
  -p <port>:80 \
  --restart=unless-stopped \
  vaultwarden/server:latest

Expected behaviour

container should start
Actual behaviour

container does not start correctly. When typing docker logs vaultwarden I get the following error
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:353:62
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:353:62
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:353:62
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:353:62
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:353:62
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:353:62
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:353:62
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:353:62
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

when starting with an additional RUST_BACKTRACE=1 I get the following
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:353:62
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: tokio::time::driver::Driver<P>::new
   4: tokio::runtime::driver::Driver::new
   5: tokio::runtime::builder::Builder::build
   6: rocket::async_main
   7: vaultwarden::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 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:353:62
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: tokio::time::driver::Driver<P>::new
   4: tokio::runtime::driver::Driver::new
   5: tokio::runtime::builder::Builder::build
   6: rocket::async_main
   7: vaultwarden::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Troubleshooting data

Duplicate issue #2563: can't start docker container (latest version on docker hub)
Created: 2022-06-18T22:26:23Z
Subject of the issue

Deployment environment





vaultwarden version: latest from dockerhub




Install method: Docker Image


Clients used: 
/


Reverse proxy and version: 
/


MySQL/MariaDB or PostgreSQL version: 
/


Other relevant details:
/


Steps to reproduce

i used, yubico, smtp and nothing more with a docker run command
Expected behaviour

that the container starts without crashing
Actual behaviour

when trying to start the container with the latest vaultwarden docker image, it instantly crashes and in portainer(a webgui for viewing containers), i see that traceback: (logs.txt)
Troubleshooting data

logs.txt
if you do have more questions, please do not hesitate, to ask them

Closing comment (2022-06-18T22:33:57Z): Duplicate of #2497