Second copy of the wiring fixed in aaa89789. apps/lnd-ui/manifest.yml still
declared network_policy: bridge with a 18083 -> 80 port mapping, while
docker/lnd-ui/nginx.conf listens on 18083 directly — it has to, so it can
proxy the backend on 127.0.0.1:5678 same-origin; the cross-origin fallback
is what broke this app on http-only nodes.
Publishing a host port to a container port where nothing listens is exactly
the failure reproduced on archi-dev-box when recreating from the matching
container-specs.sh entry: :18083 refusing connections, HTTP 000. Fixing
only the spec would have left the manifest as a live footgun for any code
path that provisions this app from its manifest instead.
Now host networking with an empty ports list, matching both what actually
runs and apps/bitcoin-ui/manifest.yml, which had it right all along.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
51 lines
1.5 KiB
YAML
51 lines
1.5 KiB
YAML
app:
|
|
id: lnd-ui
|
|
name: LND UI
|
|
version: 1.0.0
|
|
description: |
|
|
Archipelago-native HTTP frontend for LND. Runs nginx inside a
|
|
container and serves static assets. LND connection info is fetched
|
|
via an absolute URL that the host nginx routes to the archipelago
|
|
backend on 127.0.0.1:5678, so no upstream auth is baked in.
|
|
|
|
container:
|
|
build:
|
|
context: /opt/archipelago/docker/lnd-ui
|
|
dockerfile: Dockerfile
|
|
tag: localhost/lnd-ui:local
|
|
|
|
dependencies:
|
|
- app_id: lnd
|
|
|
|
resources:
|
|
memory_limit: 64Mi
|
|
|
|
security:
|
|
readonly_root: false
|
|
network_policy: host
|
|
|
|
# Host networking: the container's nginx listens on 18083 directly (see
|
|
# docker/lnd-ui/nginx.conf), because it has to proxy the archipelago backend
|
|
# on 127.0.0.1:5678 same-origin — a bridge container cannot reach that, and
|
|
# the cross-origin fallback broke the app on http-only nodes. `ports:` is
|
|
# intentionally empty because host networking bypasses port mapping, exactly
|
|
# as in apps/bitcoin-ui/manifest.yml.
|
|
#
|
|
# This previously declared `bridge` with 18083:80, which publishes the host
|
|
# port to a container port where nothing listens. scripts/container-specs.sh
|
|
# carried the identical mistake and was fixed alongside this; recreating from
|
|
# it on archi-dev-box left :18083 refusing connections.
|
|
ports: []
|
|
|
|
volumes: []
|
|
|
|
environment: []
|
|
|
|
health_check:
|
|
type: http
|
|
endpoint: http://127.0.0.1:18083
|
|
path: /
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|