Files
umbrel-apps/fulcrum/docker-compose.yml
T
Luke Childs 9f636edda0 Update app Tor sidecars to 0.4.9.11 for all affected apps
- replace every app-owned `getumbrel/tor:0.4.7.8` reference with `ghcr.io/getumbrel/tor:0.4.9.11`
- pin the public multiarch manifest list at `sha256:e382b8629c0dfef6ceb396b062622d4e4e955b19d6f16b883fd2c0723ad5671a`
- bump each affected package using `-patch.N` notation so existing installations are offered the update without implying an upstream app-version bump
- add Tor security/connectivity release notes while retaining prior upgrade warnings for users who skip releases

Affected apps: Bitcoin Knots, Bitcoin Node, Blockstream Blind Oracle, Core Lightning, Electrs, ElectrumX, Elements Core, Fulcrum, Libre Relay, Lightning Node, Monero Node, Samourai Server, Squeaknode, Suredbits Wallet, and TDEX Provider.

These packages still use Tor 0.4.7.8, which is EOL and can no longer reliably bootstrap against the current Tor network. Tor 0.4.9.11 is the current stable security patch release. The replacement image preserves Umbrel's existing `tor` entrypoint and supports both linux/amd64 and linux/arm64.
2026-07-10 22:51:40 +07:00

70 lines
2.4 KiB
YAML

version: "3.7"
services:
app_proxy:
environment:
APP_HOST: $APP_FULCRUM_IP
APP_PORT: 3006
app:
image: nmfretz/umbrel-fulcrum:1.0.1@sha256:7ebcb84446e55dbbde7711a4ac2d65ca65c55d0092e6640b41ca2d9c4539a3ff
depends_on:
- fulcrum
restart: on-failure
environment:
ELECTRUM_HIDDEN_SERVICE: "${APP_FULCRUM_RPC_HIDDEN_SERVICE}"
ELECTRUM_LOCAL_SERVICE: "${DEVICE_DOMAIN_NAME}"
ELECTRUM_HOST: "${APP_FULCRUM_NODE_IP}"
ELECTRUM_PUBLIC_CONNECTION_PORT: ${APP_FULCRUM_NODE_PORT}
BITCOIN_HOST: "${APP_BITCOIN_NODE_IP}"
RPC_USER: "${APP_BITCOIN_RPC_USER}"
RPC_PASSWORD: "${APP_BITCOIN_RPC_PASS}"
RPC_PORT: "${APP_BITCOIN_RPC_PORT}"
volumes:
- "${APP_DATA_DIR}/data/fulcrum-logs:/fulcrum-logs"
networks:
default:
ipv4_address: $APP_FULCRUM_IP
fulcrum:
image: cculianu/fulcrum:v2.1.1@sha256:72d8b2f9142f83a51c6c3ba2f6931b496a08bede610b28ef2315b87aa1e3bb64
init: true
# Rely on Docker's default SIGTERM; Fulcrum treats SIGTERM/SIGINT/SIGQUIT as graceful
# Generous grace period prevents SIGKILL during checkpoint/flush on exit
stop_grace_period: 5m
restart: on-failure
user: "1000:1000"
environment:
TCP: 0.0.0.0:${APP_FULCRUM_NODE_PORT}
ADMIN: 0.0.0.0:${APP_FULCRUM_ADMIN_PORT}
BITCOIND: ${APP_BITCOIN_NODE_IP}:${APP_BITCOIN_RPC_PORT}
RPCUSER: ${APP_BITCOIN_RPC_USER}
RPCPASSWORD: ${APP_BITCOIN_RPC_PASS}
PEERING: "false"
ANNOUNCE: "false"
DATA_DIR: /data
# Exec Fulcrum as PID1 so it receives SIGTERM directly; FIFO+tee mirrors output to docker logs and /logs/fulcrum.log
# rm -f makes FIFO creation idempotent across restarts/crash loops
command: >
sh -c 'rm -f /tmp/fulcrum.pipe; mkfifo /tmp/fulcrum.pipe;
tee -a /logs/fulcrum.log < /tmp/fulcrum.pipe &
exec Fulcrum -D /data _ENV_ > /tmp/fulcrum.pipe 2>&1'
volumes:
- "${APP_DATA_DIR}/data/fulcrum:/data"
- "${APP_DATA_DIR}/data/fulcrum-logs:/logs"
ports:
- "${APP_FULCRUM_NODE_PORT}:${APP_FULCRUM_NODE_PORT}"
networks:
default:
ipv4_address: $APP_FULCRUM_NODE_IP
tor:
image: ghcr.io/getumbrel/tor:0.4.9.11@sha256:e382b8629c0dfef6ceb396b062622d4e4e955b19d6f16b883fd2c0723ad5671a
user: "1000:1000"
restart: on-failure
volumes:
- ${APP_DATA_DIR}/torrc:/etc/tor/torrc:ro
- ${TOR_DATA_DIR}:/data
environment:
HOME: "/tmp"