Repository navigation
fix: remove fixed service container names (SPEC-C02) - #102
Conversation
|
Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 06b7915 This is a development version and should only be installed for testing purposes.
Hash: (by dappnodebot/build-action) |
✅ Package harness passed
Run overview
Baseline vs candidate
Container comparison
Container inventoryBaseline
Candidate
Runtime analysis advisory✅ Clean — Heuristic and Nexus analysis: No likely new runtime regression is evident. The candidate retains the baseline's gateway-mode, command-owner, plaintext-token, and LAN-binding warnings, while plugin and skill availability improve and the prior permission and missing-requirement findings disappear.
✅ No new runtime findings were reported. Cleanup and diagnostics
✅ No run errors were recorded. Deterministic checks decide the verdict. Runtime log analysis is advisory. TropiBot publishes bounded summaries and never posts raw logs. |
Context
Correct SPEC-C02 from the package specification checks.
Stacked on #101 (base
fix/spec-m03-upstream-metadata). Merge the base PR first; this diff contains only the next focused fix.Approach
Remove fixed container names from package services; DAPPMANAGER supplies those names at installation. Keep empty variant service overrides as {} so they still inherit the root service.
Test instructions
Run the SDK package-spec validation on this branch for all package variants.
Verified locally:
docker compose config --quietpass for every variant.git diff --checkand replay of the complete PR stack pass.Full container images were not built locally.