mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #1320] Docker install fails #914
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#914
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jackald on GitHub (Jan 20, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1320
Subject of the issue
Docker install fails
Your environment
Docker image image: bitwardenrs/server:latest pulled today
Bitwarden_rs version:
| Version 1.18.0 |
Install method: Docker
Clients used:
Client: Docker Engine - Community
Version: 20.10.2
Steps to reproduce
Stack used in portainer:
version: 2
services:
BitwardenRS:
image: bitwardenrs/server:latest
container_name: BitwardenRS
volumes:
- /srv/b7ee8e59-561e-41ad-b896-e8dca8accc33/Docker/BitWardenRS:/data
ports:
- 8086:80
restart: unless-stopped
Expected behaviour
Container to start and the web gui to be reachable
Actual behaviour
The container erros with 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")': src/db/mod.rs:275
Relevant logs
/--------------------------------------------------------------------\
| Starting Bitwarden_RS |
| Version 1.18.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://bitwardenrs.discourse.group/ |
| Report suspected bugs/issues in the software itself at: |
| https://github.com/dani-garcia/bitwarden_rs/issues/new |
--------------------------------------------------------------------/
FO] No .env file found.
[2021-01-20 22:54:23.576][panic][ERROR] thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")': src/db/mod.rs:275
0: bitwarden_rs::init_logging::{{closure}}
1: std::panicking::rust_panic_with_hook
2: std::panicking::begin_panic_handler::{{closure}}
3: std::sys_common::backtrace::__rust_end_short_backtrace
4: rust_begin_unwind
5: core::panicking::panic_fmt
6: core::option::expect_none_failed
7: bitwarden_rs::db::sqlite_migrations::run_migrations
8: bitwarden_rs::db::DbPool::from_config
9: bitwarden_rs::util::retry_db
10: bitwarden_rs::main
11: std::sys_common::backtrace::__rust_begin_short_backtrace
12: std::rt::lang_start::{{closure}}
13: core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once
14: main
15: __libc_start_main
16: _start
@BlackDex commented on GitHub (Jan 20, 2021):
You seem to be using some kind of shared storage for your /data folder. Shared/Network storage is know to cause some issues. So either disable wal using the configuration or use a different database.
@jackald commented on GitHub (Jan 21, 2021):
Turning of wal worked thank you.