Skip to content

fix: robust Exegol container detection (no stale pinning)#8

Merged
Dxsk merged 1 commit into
mainfrom
fix/exegol-detection
Jun 10, 2026
Merged

fix: robust Exegol container detection (no stale pinning)#8
Dxsk merged 1 commit into
mainfrom
fix/exegol-detection

Conversation

@Dxsk

@Dxsk Dxsk commented Jun 10, 2026

Copy link
Copy Markdown
Owner

Problem

A stale EXEGOL_CONTAINER in ~/.config/dotenvsec/config (e.g. a removed container) short-circuited auto-detection (if [[ -z … ]]), so dotsec exegol failed with "No such container". The value also got pinned per-engagement, propagating the stale name.

Fix

  • __dotsec_load_global now re-detects when EXEGOL_CONTAINER is unset or the configured container doesn't exist (docker container inspect), preferring a running container (then any). A dead value never sticks.
  • config/global-defaults: no longer pins EXEGOL_CONTAINER (commented → auto-detect by default).
  • Template/cmd_new: stop reinjecting EXEGOL_CONTAINER into the engagement .env — it's global infra, not per-engagement (the old sed targeted exegol-default, which never matched anyway — dead code removed).

Test Plan

  • make test — 61/61 (new: re-detects when configured container is gone, via docker stub)
  • make lint — shellcheck clean

@Dxsk Dxsk merged commit e2897be into main Jun 10, 2026
4 checks passed
@Dxsk Dxsk deleted the fix/exegol-detection branch June 10, 2026 20:48
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