gortium/infra
1
1
Fork 0
Code Issues 13 Pull Requests 21 Actions Packages Projects 1 Releases Wiki Activity

fix: update compose submodule to pick up backup network fix (external→bridge) #66

New Issue
Open
opened 2026-05-22 19:23:28 +00:00 by Hermes · 0 comments
Hermes commented 2026-05-22 19:23:28 +00:00
Collaborator
Copy Link

Problem

backup_stack.service is failing because the deployed Nix store copy of assets/compose/backup/compose.yml still has networks.backup_net.external: true, but the network was never created externally.

The compose repo fix (PR #45, commit d7449e9) was already merged: backup/compose.yml now uses driver: bridge which lets Docker Compose auto-create the network.

Root Cause

The infra repo's compose submodule still points to c9aacc5 (a pre-fix commit), not to d7449e9 (the merged fix). Since nixos-rebuild switch copies the compose files from the submodule at build time, the deployed version still has external: true.

Fix

Update assets/compose submodule to the latest master of the compose repo (d7449e9).

Validation

After merging and deploying (nixos-rebuild switch --flake .#lazyworkhorse), verify:

systemctl restart backup_stack.service
systemctl status backup_stack.service
## Problem `backup_stack.service` is failing because the deployed Nix store copy of `assets/compose/backup/compose.yml` still has `networks.backup_net.external: true`, but the network was never created externally. The compose repo fix (PR #45, commit `d7449e9`) was already merged: `backup/compose.yml` now uses `driver: bridge` which lets Docker Compose auto-create the network. ## Root Cause The infra repo's compose submodule still points to `c9aacc5` (a pre-fix commit), not to `d7449e9` (the merged fix). Since `nixos-rebuild switch` copies the compose files from the submodule at build time, the deployed version still has `external: true`. ## Fix Update `assets/compose` submodule to the latest master of the compose repo (`d7449e9`). ## Validation After merging and deploying (`nixos-rebuild switch --flake .#lazyworkhorse`), verify: ```bash systemctl restart backup_stack.service systemctl status backup_stack.service ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Hermes gortium
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gortium/infra#66
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?