Skip to content

fix(cli): stale .env can no longer wedge stacklet stop - #95

Merged
arthware-dev merged 1 commit into
mainfrom
fix/stacklet-down-stale-env
Sep 15, 2026
Merged

arthware-dev merged 1 commit into
mainfrom
fix/stacklet-down-stale-env

Conversation

@arthware-dev

Copy link
Copy Markdown
Contributor

./stack down memory (and restart, which calls down) failed with "unknown error" and could not stop the container.

Root cause: the media-archive merge added ${MEDIA_ARCHIVE_DIR}:/vault/media:ro to the memory compose file, but the deployed .env predated it, so the variable was blank and compose rejected the whole file (invalid spec: :/vault/media:ro: empty section between colons). compose reads the file before any action, so even stop was invalid. up re-renders .env every time; down only did so when .env was missing, so a stale one wedged the stacklet.

Fix:

  • CLI.down always re-renders .env before compose stop, mirroring up.
  • Surface the compose error instead of the generic "unknown error".
  • Two regression tests.

Not specific to memory: any stacklet that gains a compose variable hits this until env is regenerated.

A stale .env missing a merged-in variable (MEDIA_ARCHIVE_DIR) made
compose reject every command; down now refreshes env like up, and
surfaces the compose error instead of 'unknown error'.
@arthware-dev
arthware-dev merged commit 4b2389f into main Sep 15, 2026
1 check passed
@arthware-dev
arthware-dev deleted the fix/stacklet-down-stale-env branch September 22, 2026 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant