[GH-ISSUE #1110] Panic when using a data volume passed through VM #786

Closed
opened 2026-03-03 02:03:11 +03:00 by kerem · 1 comment
Owner

Originally created by @dl-lim on GitHub (Aug 22, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1110

I'm trying to install bitwardenrs/server docker image with data volume. Docker is run on a ubuntu 20.04.1 VM on proxmox.

Data volume is a zfs passed via virtio-fs into the VM. Works seamlessly for most things when mounted appropriately with fstab.

So I've tested installing bitwarden docker with and without docker volume. Works fine without docker volume, but this would bloat the VM image. So I'd prefer to have the data placed in the volume outside the image. And that's when this error occurs. Only happens with using a docker volume. If using the auto-generated volume that is within the image, it works fine. Any ideas?

The log is as below (sorry, not sorry for not using the code tags - the formatting goes awful with it)

1: std::panicking::rust_panic_with_hook,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:530,
2: rust_begin_unwind,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:437,
3: core::panicking::panic_fmt,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/panicking.rs:85,
4: core::option::expect_none_failed,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/option.rs:1269,
5: bitwarden_rs::main,
6: std::rt::lang_start::{{closure}},
7: std::rt::lang_start_internal::{{closure}},
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:52,
std::panicking::try::do_call,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:348,
std::panicking::try,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:325,
std::panic::catch_unwind,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panic.rs:394,
std::rt::lang_start_internal,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:51,
8: main,
9: __libc_start_main,
10: _start,
,
/--------------------------------------------------------------------,
| Starting Bitwarden_RS |,
| Version 1.16.3 |,
|--------------------------------------------------------------------|,
| 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://bitwardenrs.discourse.group/ |,
| Report suspected bugs/issues in the software itself at: |,
| https://github.com/dani-garcia/bitwarden_rs/issues/new |,
--------------------------------------------------------------------/,
,
[2020-08-22 18:07:59.257][panic][ERROR] thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")': src/main.rs:232,
0: bitwarden_rs::init_logging::{{closure}},
1: std::panicking::rust_panic_with_hook,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:530,
2: rust_begin_unwind,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:437,
3: core::panicking::panic_fmt,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/panicking.rs:85,
4: core::option::expect_none_failed,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/option.rs:1269,
5: bitwarden_rs::main,
6: std::rt::lang_start::{{closure}},
7: std::rt::lang_start_internal::{{closure}},
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:52,
std::panicking::try::do_call,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:348,
std::panicking::try,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:325,
std::panic::catch_unwind,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panic.rs:394,
std::rt::lang_start_internal,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:51,
8: main,
9: __libc_start_main,
10: _start,
,
/--------------------------------------------------------------------,
| Starting Bitwarden_RS |,
| Version 1.16.3 |,
|--------------------------------------------------------------------|,
| 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://bitwardenrs.discourse.group/ |,
| Report suspected bugs/issues in the software itself at: |,
| https://github.com/dani-garcia/bitwarden_rs/issues/new |,
--------------------------------------------------------------------/,
,
[2020-08-22 18:08:59.523][panic][ERROR] thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")': src/main.rs:232,
0: bitwarden_rs::init_logging::{{closure}},
1: std::panicking::rust_panic_with_hook,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:530,
2: rust_begin_unwind,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:437,
3: core::panicking::panic_fmt,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/panicking.rs:85,
4: core::option::expect_none_failed,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/option.rs:1269,
5: bitwarden_rs::main,
6: std::rt::lang_start::{{closure}},
7: std::rt::lang_start_internal::{{closure}},
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:52,
std::panicking::try::do_call,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:348,
std::panicking::try,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:325,
std::panic::catch_unwind,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panic.rs:394,
std::rt::lang_start_internal,
at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:51,
8: main,
9: __libc_start_main,
10: _start,
,

Originally created by @dl-lim on GitHub (Aug 22, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1110 I'm trying to install bitwardenrs/server docker image with data volume. Docker is run on a ubuntu 20.04.1 VM on proxmox. Data volume is a zfs passed via virtio-fs into the VM. Works seamlessly for most things when mounted appropriately with fstab. So I've tested installing bitwarden docker with and without docker volume. Works fine without docker volume, but this would bloat the VM image. So I'd prefer to have the data placed in the volume outside the image. And that's when this error occurs. Only happens with using a docker volume. If using the auto-generated volume that is within the image, it works fine. Any ideas? The log is as below (sorry, not sorry for not using the code tags - the formatting goes awful with it) 1: std::panicking::rust_panic_with_hook, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:530, 2: rust_begin_unwind, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:437, 3: core::panicking::panic_fmt, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/panicking.rs:85, 4: core::option::expect_none_failed, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/option.rs:1269, 5: bitwarden_rs::main, 6: std::rt::lang_start::{{closure}}, 7: std::rt::lang_start_internal::{{closure}}, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:52, std::panicking::try::do_call, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:348, std::panicking::try, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:325, std::panic::catch_unwind, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panic.rs:394, std::rt::lang_start_internal, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:51, 8: main, 9: __libc_start_main, 10: _start, , /--------------------------------------------------------------------\, | Starting Bitwarden_RS |, | Version 1.16.3 |, |--------------------------------------------------------------------|, | 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://bitwardenrs.discourse.group/ |, | Report suspected bugs/issues in the software itself at: |, | https://github.com/dani-garcia/bitwarden_rs/issues/new |, \--------------------------------------------------------------------/, , [2020-08-22 18:07:59.257][panic][ERROR] thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")': src/main.rs:232, 0: bitwarden_rs::init_logging::{{closure}}, 1: std::panicking::rust_panic_with_hook, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:530, 2: rust_begin_unwind, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:437, 3: core::panicking::panic_fmt, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/panicking.rs:85, 4: core::option::expect_none_failed, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/option.rs:1269, 5: bitwarden_rs::main, 6: std::rt::lang_start::{{closure}}, 7: std::rt::lang_start_internal::{{closure}}, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:52, std::panicking::try::do_call, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:348, std::panicking::try, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:325, std::panic::catch_unwind, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panic.rs:394, std::rt::lang_start_internal, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:51, 8: main, 9: __libc_start_main, 10: _start, , /--------------------------------------------------------------------\, | Starting Bitwarden_RS |, | Version 1.16.3 |, |--------------------------------------------------------------------|, | 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://bitwardenrs.discourse.group/ |, | Report suspected bugs/issues in the software itself at: |, | https://github.com/dani-garcia/bitwarden_rs/issues/new |, \--------------------------------------------------------------------/, , [2020-08-22 18:08:59.523][panic][ERROR] thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")': src/main.rs:232, 0: bitwarden_rs::init_logging::{{closure}}, 1: std::panicking::rust_panic_with_hook, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:530, 2: rust_begin_unwind, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:437, 3: core::panicking::panic_fmt, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/panicking.rs:85, 4: core::option::expect_none_failed, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libcore/option.rs:1269, 5: bitwarden_rs::main, 6: std::rt::lang_start::{{closure}}, 7: std::rt::lang_start_internal::{{closure}}, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:52, std::panicking::try::do_call, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:348, std::panicking::try, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panicking.rs:325, std::panic::catch_unwind, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/panic.rs:394, std::rt::lang_start_internal, at rustc/daecab3a784f28082df90cebb204998051f3557d/src/libstd/rt.rs:51, 8: main, 9: __libc_start_main, 10: _start, ,
kerem closed this issue 2026-03-03 02:03:11 +03:00
Author
Owner

@dl-lim commented on GitHub (Aug 23, 2020):

Using env flag ENABLE_DB_WAL=false and recreating solved it.

<!-- gh-comment-id:678746793 --> @dl-lim commented on GitHub (Aug 23, 2020): Using env flag ENABLE_DB_WAL=false and recreating solved it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#786
No description provided.