Files
umbrel-apps/bisq2-node/docker-compose.yml
T
d7fb413aca Release Bisq 2 Node 2.1.14.0 (#6203)
Co-authored-by: bisq-mobile-ci <ci@bisq.network>
Co-authored-by: nmfretz <nmfretz@gmail.com>
2026-10-19 15:50:17 +10:00

32 lines
1.3 KiB
YAML

# Bisq 2 Node — a headless Bisq 2 node (api-app) plus a small nginx web UI that shows node
# status and a pairing QR code for the Bisq Connect mobile app.
#
# The node's API binds 127.0.0.1:8090 (loopback only) for security. The `web` sidecar runs with
# `network_mode: "service:server"` so it shares the node's network namespace — that lets it read
# the loopback API for the status check and serve its own :8091. Because `web` has no network
# identity of its own, `app_proxy` targets the `server` container (which owns the namespace + :8091).
# Umbrel's authenticated app_proxy is the only ingress; PROXY_AUTH_ADD is intentionally left unset
# so auth stays ON (the pairing code grants node access, so it must never be exposed unauthenticated).
version: "3.7"
services:
app_proxy:
environment:
APP_HOST: bisq2-node_server_1
APP_PORT: 8091
server:
image: ghcr.io/bisq-network/bisq2-api:2.1.14.0@sha256:5b028dbe98353fae10d49d8d69f864a7ef9d294647d868c127f66c9f6a4f0a64
restart: on-failure
stop_grace_period: 1m
mem_limit: 2g
volumes:
- ${APP_DATA_DIR}/data:/data
web:
image: ghcr.io/bisq-network/bisq2-api-web-ui:2.1.14.0@sha256:3e010e4ca8031d07c64a9b1459f603d5d2db6953edfddad95940c4a5fc68a950
restart: on-failure
network_mode: "service:server"
volumes:
- ${APP_DATA_DIR}/data:/data:ro