[BUG] Bitcoin Knots does not shut down cleanly on docker stop (Wayland)
Chưa có ai nhận issue này.
Đánh giá
- Độ khó
- 4/5
- Thời gian dự kiến
- 3-5 ngày
- Mức phù hợp với người mới
- 38/100
- Loại issue
- Lỗi
- Độ rõ ràng
- Khá rõ ràng
- Mức độ hoạt động
- Sôi nổi
- Công nghệ
- docker, linux
- Lĩnh vực
- devops, infrastructure
Hướng nghiên cứu
The report points to the default /init entrypoint, Wayland desktop startup, and Bitcoin Knots shutdown logs; it does not identify a specific source file or failing test. Start by tracing how container stop signals reach Bitcoin Qt and the desktop processes, then reproduce the reported docker stop run and compare it with the bitcoin-cli stop control. Done means Bitcoin logs Shutdown: done before the desktop/compositor terminates.
Do mô hình lập chỉ mục viết ra từ nội dung của issue.
Mô tả
Is there an existing issue for this?
- I have searched the existing issues.
Current Behavior
With the unmodified image and default Wayland startup, docker stop --timeout 120 breaks Bitcoin Qt's Wayland connection without logging Shutdown: done (4/4 ordinary-stop runs).
The full logs below are from one fresh offline run. Docker stopped in 3.669 seconds, with container exit 0 and OOMKilled=false. The desktop log reports clean termination, but Bitcoin's own log ends with the broken-Wayland error. Container exit 0 does not establish clean application shutdown.
Control: explicitly calling local bitcoin-cli -datadir=/config/.bitcoin stop as abc with HOME=/config produced Shutdown: done before stopping the container in a separate run. The exact image/service cause is not yet isolated.
Expected Behavior
Bitcoin Knots completes its application shutdown before the desktop/compositor is terminated.
Steps To Reproduce
- Create a fresh disposable
/config/.bitcoin/bitcoin.conf, owned by UID/GID 1000, containing:server=1 listen=0 networkactive=0 prune=10240 upnp=0 natpmp=0 dbcache=512 - Create/start the container below. Wait for
bitcoin-qt,labwcand successful local RPC:docker exec knots-full-log-control-20261010 runuser -u abc -- env HOME=/config bitcoin-cli -datadir=/config/.bitcoin getblockchaininfo - Run
docker stop --timeout 120 knots-full-log-control-20261010, without preceding RPC stop. - Before any restart, collect
docker logs knots-full-log-control-20261010and inspect/config/.bitcoin/debug.log: broken Wayland connection, noShutdown: done.
No wallet, synchronization or peer connection is needed.
Environment
- OS: Debian GNU/Linux 13 (trixie); kernel
7.0.14-20-pve. - How docker service was installed: Docker CE Debian packages (
docker-ce/docker-ce-cli,5:29.8.2-1~debian.13~trixie) from the official Docker APT repository; Engine 29.8.2. - Docker runs inside an unprivileged Proxmox LXC; no VM/bare-metal Docker control.
- Image build:
29.4.knots20260508.2-resolute1-ls49; Bitcoin Knotsv29.4.2.knots20260508. - Default
/initentrypoint and Wayland desktop, no service/image patches or GPU. Offline fresh data, no published ports.
CPU architecture
x86-64
Docker creation
docker create --name knots-full-log-control-20261010 \
--label hermes.knots.full-log-control=20261010 \
--platform linux/amd64 --network none --restart no \
--cpus 2 --memory 4g --memory-swap 5g --shm-size 1g \
-e PUID=1000 -e PGID=1000 -e TZ=Etc/UTC \
--mount type=bind,src=/path/to/disposable/config,dst=/config \
lscr.io/linuxserver/bitcoin-knots@sha256:3816fd7d5e7df5a89938f5b7b689aad64faf24b6a3875435f8950bce7eab8a95
docker start knots-full-log-control-20261010
/path/to/disposable/config represents the dedicated disposable bind directory used for this run.
Container logs
Full output of docker logs knots-full-log-control-20261010, captured after stopping and before any restart/removal (stdout and stderr, unfiltered).
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 1000
User GID: 1000
───────────────────────────────────────
Linuxserver.io version: 29.4.knots20260508.2-resolute1-ls49
Build-date: 2026-09-29T00:04:16+00:00
───────────────────────────────────────
............+..+.........+++++++++++++++++++++++++++++++++++++++*.......+.+.....+...+............+.+...+++++++++++++++++++++++++++++++++++++++*...+...+.+...........+....+......+.........+..+.......+..+...+.+.....+.+.....+......+....+...+.....+.......+......+............+...+..+.+..+.......+..+...+......+....+......+.....+.........+......+......+....+.................+...+.+.........+..+.......+.....+.......+........+.+............+...+.....+....+..+..........++++++
....+....+.....+++++++++++++++++++++++++++++++++++++++*....+.....+.+..+...+.+...+...+...............+...+.....+.+.........+..+.........+.........+......+......+++++++++++++++++++++++++++++++++++++++*..............+.......+...+..+............+.........+.+.....+.+...+..+...+.+...........+...............+......................+..+.........+.+......+..+...........................+...+.+............+.....+.........+.+...+...........++++++
-----
[ls.io-init] Creating initial backup of menu.xml
[ls.io-init] Generating labwc rc.xml from template
[custom-init] No custom files found, skipping...
[svc-de] Wayland mode: Waiting for socket at /config/.XDG/wayland-1...
[ls.io-init] done.
19
20
[pixelflux] No hardware encoder on render node 0 (nvenc): Could not load CUDA library (libcuda.so.1): dlopen failed
[pixelflux] Thread priority -15 refused and rtkit does not grant it; capture threads run at normal priority.
[Wayland] Renderer: software (Pixman), no render node.
[Wayland] View 1 created over output 0: 1024x768 @ (0, 0).
[Wayland] Socket listening on: "wayland-1"
INFO:server:Wayland compositor socket: wayland-1
INFO:main:Selkies 2.0.0 starting: websockets transport, Wayland capture, encoder h264enc at 8-240 fps, sized by the client, audio on, gamepads off, access open.
INFO:server:Starting service: websockets
INFO:gamepad:4 virtual gamepads ready ('Microsoft X-Box 360 pad', sockets under /tmp); kernel uinput off.
INFO:input:Wayland clipboard: native compositor callback active (no polling).
INFO:input:Apps panel enabled: selkies-proot can run here.
INFO:input:Apps installed in this session: none
[svc-de] /config/.XDG/wayland-1 found launching de
INFO:server:Selkies server running on http://[::1]:8082, http://127.0.0.1:8082
INFO:printing:Print queue Selkies listening on /config/.XDG/selkies-cups/cups.sock, spooling to /config/.local/state/selkies/print
INFO:input:Wayland app compositor 'wayland-0' (auto-detected); routing input + clipboard there, capture stays on 'wayland-1'.
INFO:input:Wayland clipboard: app-compositor data-control watch active (no forks).
Waiting up to 5 seconds for desktop processes to terminate...
Io error: Broken pipe (os error 32)
[Clipboard] app-compositor watch ended: read: Io error: Broken pipe (os error 32)
All desktop processes terminated cleanly.
INFO:main:Received SIGTERM, shutting down
INFO:server:Shutdown signal received...
INFO:server:Stopping service: websockets
WARNING:ws:No display clients connected. Video pipelines remain stopped.
INFO:ws:DataStreamingServer shutdown complete.
Full application debug.log from the same fresh run
2026-10-10T23:58:05Z Bitcoin Knots version v29.4.2.knots20260508 (release build)
2026-10-10T23:58:05Z parameter interaction: -listen=0 -> setting -discover=0
2026-10-10T23:58:05Z parameter interaction: -listen=0 -> setting -listenonion=0
2026-10-10T23:58:05Z parameter interaction: -listen=0 -> setting -i2pacceptincoming=0
2026-10-10T23:58:05Z Qt 6.10.2 (dynamic), plugin=wayland
2026-10-10T23:58:05Z No static plugins.
2026-10-10T23:58:05Z Style: fusion / QFusionStyle
2026-10-10T23:58:05Z System: Ubuntu 26.04.1 LTS, x86_64-little_endian-lp64
2026-10-10T23:58:05Z Screen: WL-1 1280x720, pixel ratio=1.0
2026-10-10T23:58:05Z ParameterInteraction: parameter interaction: -walletimplicitsegwit=0 -> setting -addresstype=legacy
2026-10-10T23:58:05Z Using the 'sse4(1way);sse41(4way);avx2(8way)' SHA256 implementation
2026-10-10T23:58:05Z Using RdSeed as an additional entropy source
2026-10-10T23:58:05Z Using RdRand as an additional entropy source
2026-10-10T23:58:05Z Default data directory /config/.bitcoin
2026-10-10T23:58:05Z Using data directory /config/.bitcoin
2026-10-10T23:58:05Z Config file: /config/.bitcoin/bitcoin.conf
2026-10-10T23:58:05Z R/W Config file: /config/.bitcoin/bitcoin_rw.conf (not found, skipping)
2026-10-10T23:58:05Z Config file arg: dbcache="512"
2026-10-10T23:58:05Z Config file arg: listen="0"
2026-10-10T23:58:05Z Config file arg: natpmp="0"
2026-10-10T23:58:05Z Config file arg: networkactive="0"
2026-10-10T23:58:05Z Config file arg: prune="10240"
2026-10-10T23:58:05Z Config file arg: server="1"
2026-10-10T23:58:05Z Config file arg: upnp="0"
2026-10-10T23:58:05Z Using at most 125 automatic connections (1024 file descriptors available)
2026-10-10T23:58:05Z scheduler thread start
2026-10-10T23:58:05Z Binding RPC on address ::1 port 8332
2026-10-10T23:58:05Z Binding RPC on address 127.0.0.1 port 8332
2026-10-10T23:58:05Z Generated RPC authentication cookie /config/.bitcoin/.cookie
2026-10-10T23:58:05Z Permissions used for cookie: rw-------
2026-10-10T23:58:05Z Using random cookie authentication.
2026-10-10T23:58:05Z Starting HTTP server with 16 worker threads
2026-10-10T23:58:05Z Using wallet directory /config/.bitcoin
2026-10-10T23:58:05Z init message: Verifying wallet(s)…
2026-10-10T23:58:05Z Using /16 prefix for IP bucketing
2026-10-10T23:58:05Z init message: Loading P2P addresses…
2026-10-10T23:58:05Z Creating peers.dat because the file was not found ("/config/.bitcoin/peers.dat")
2026-10-10T23:58:05Z init message: Loading banlist…
2026-10-10T23:58:05Z Recreating the banlist database
2026-10-10T23:58:05Z SetNetworkActive: false
2026-10-10T23:58:05Z /config/.bitcoin/fee_estimates.dat is not found. Continue anyway.
2026-10-10T23:58:05Z Cache configuration:
2026-10-10T23:58:05Z * Using 2.0 MiB for block index database
2026-10-10T23:58:05Z * Using 8.0 MiB for chain state database
2026-10-10T23:58:05Z * Using 502.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2026-10-10T23:58:05Z Script verification uses 11 additional threads
2026-10-10T23:58:05Z Using obfuscation key for blocksdir *.dat files (/config/.bitcoin/blocks): '7d5cd40efc9624ee'
2026-10-10T23:58:05Z Opening LevelDB in /config/.bitcoin/blocks/index
2026-10-10T23:58:05Z Opened LevelDB successfully
2026-10-10T23:58:05Z Using obfuscation key for /config/.bitcoin/blocks/index: 0000000000000000
2026-10-10T23:58:05Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2026-10-10T23:58:05Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2026-10-10T23:58:05Z init message: Loading block index…
2026-10-10T23:58:05Z Assuming ancestors of block 0000000000000078ed1e20cac1acf78df6d1060c78059fb6331e17141c881fc8 have valid signatures.
2026-10-10T23:58:05Z Setting nMinimumChainWork=00000000000000000000000000000000000000013e00277374c9f9eeadc70200
2026-10-10T23:58:05Z Prune configured to target 10240 MiB on disk for block and undo files.
2026-10-10T23:58:05Z LoadBlockIndexDB: last block file = 0
2026-10-10T23:58:05Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2026-10-10T23:58:05Z Checking all blk files are present...
2026-10-10T23:58:05Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2026-10-10T23:58:05Z Opening LevelDB in /config/.bitcoin/chainstate
2026-10-10T23:58:05Z Opened LevelDB successfully
2026-10-10T23:58:05Z Wrote new obfuscation key for /config/.bitcoin/chainstate: 7623316d4871f99d
2026-10-10T23:58:05Z Using obfuscation key for /config/.bitcoin/chainstate: 7623316d4871f99d
2026-10-10T23:58:05Z init message: Revalidating blocks…
2026-10-10T23:58:05Z init message: Verifying blocks…
2026-10-10T23:58:05Z Block index and chainstate loaded
2026-10-10T23:58:05Z init message: Pruning blockstore…
2026-10-10T23:58:05Z initload thread start
2026-10-10T23:58:05Z UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x00000001 log2_work=32.000022 tx=1 date='2009-01-03T18:15:05Z' progress=0.000000 cache=0.3MiB(0txo)
2026-10-10T23:58:05Z block tree size = 1
2026-10-10T23:58:05Z nBestHeight = 0
2026-10-10T23:58:05Z Failed to open mempool file. Continuing anyway.
2026-10-10T23:58:05Z initload thread exit
2026-10-10T23:58:05Z 0 block-relay-only anchors will be tried for connections.
2026-10-10T23:58:05Z init message: Starting network threads…
2026-10-10T23:58:05Z net thread start
2026-10-10T23:58:05Z addcon thread start
2026-10-10T23:58:05Z dnsseed thread start
2026-10-10T23:58:05Z init message: Done loading
2026-10-10T23:58:05Z Waiting for network to be reactivated before querying DNS seeds.
2026-10-10T23:58:05Z opencon thread start
2026-10-10T23:58:05Z msghand thread start
2026-10-10T23:58:05Z GUI: Platform customization: "other"
2026-10-10T23:58:06Z GUI: The Wayland connection broke. Did the Wayland compositor die?
- Ngôn ngữ chính
- Dockerfile
- Star
- 5
- Fork
- 0
- Chỉ số merge pull request
- Không có pull request nào được merge trong 30 ngày
Chuẩn bị môi trường
- Có Dockerfile hoặc tệp Docker Compose
- Có mẫu pull request
- Đọc hướng dẫn đóng góp
Bắt đầu từ đâu
- Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
- Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
- Fork repository và làm thay đổi trên một nhánh.
- Mở pull request có tham chiếu số hiệu của issue.
Issue tương tự
-
windows-artifacts: the win-arm64 job uses a Visual Studio generator missing from windows-11-armĐang mở
Độ khó 1/5 Dưới một giờ Mức phù hợp với người mới 86/100
-
Own-agent checks: reject the Actions bot id in admit.mjs and test the source label in pr-verifyĐang mở
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 74/100
melodic-software/claude-code-plugins#17374 · 2 bình luận ·
Maintainer thường phản hồi trong vòng 1 ngày
-
area: doc-engine area: infrastructure bug community-request
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 75/100
snapotter-hq/SnapOtter#4834 ·
Maintainer thường phản hồi trong vòng 1 ngày
-
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 78/100
-
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 73/100
soroswap/token-list#125 ·
Maintainer thường phản hồi trong vòng 1 ngày