Files
computer-playbook/roles/web-app-bluesky/meta/volumes.yml
kevinveenbirkenbachandClaude Opus 4.8 b25e34ca5e fix(web-app-bluesky): stage pdsadmin before deploy and keep it a bind mount
The pdsadmin binary is mounted from the volumes dir, but 02_pds.yml ran only
after the sys-stk-front-proxy include whose flush already deploys the stack, so
the deploy aborted on the missing source. Move the PDS staging ahead of the
front-proxy block. Also revert pdsadmin from a docker config back to a bind
mount: it is a ~9MB Go binary and swarm configs are capped at ~1MB, so type:
config fails stack deploy. The pds service is manager-pinned, so the
manager-staged bind source is always present on the node that runs it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-03 00:26:05 +02:00

15 lines
312 B
YAML

---
pds_data:
type: volume
mounts:
- service: pds
target: /opt/pds
pdsadmin:
type: bind
source: "{{ [lookup('container', 'web-app-bluesky', 'directories.volumes'), 'pdsadmin', 'pdsadmin'] | path_join }}"
mounts:
- service: pds
target: /usr/local/bin/pdsadmin
read_only: true