lc silently ignores container: in astra.yaml. The spec still validates, and ASTRA's own examples use it.
Repro (lightcone-cli 0.5.0rc2):
lc init lc-iris && cd lc-iris
cp <astra-tools>/examples/iris/astra.yaml . # has `container: python:3.12-slim`
rm universes/* && cp <astra-tools>/examples/iris/universes/* universes/
git add -A && git commit -m iris
lc materialize --check
This plans 12 runs with no warning. lc status reports mode: direct, so recipes would run in the host .venv, not in python:3.12-slim.
CLAUDE.md records that container: in astra.yaml was deliberately removed in favour of [tool.lightcone.image], so the removal isn't the bug. The bug is that it's silent: someone who copies ASTRA's canonical example thinks their analysis runs in a container when it doesn't, and that's a provenance problem.
Suggestion: when the spec sets container:, warn (or refuse) and point to [tool.lightcone.image] in pyproject.toml. It may also be worth raising with astra-spec / astra-tools whether the examples should still use the field.
lcsilently ignorescontainer:inastra.yaml. The spec still validates, and ASTRA's own examples use it.Repro (lightcone-cli 0.5.0rc2):
This plans 12 runs with no warning.
lc statusreportsmode: direct, so recipes would run in the host.venv, not inpython:3.12-slim.CLAUDE.md records that
container:inastra.yamlwas deliberately removed in favour of[tool.lightcone.image], so the removal isn't the bug. The bug is that it's silent: someone who copies ASTRA's canonical example thinks their analysis runs in a container when it doesn't, and that's a provenance problem.Suggestion: when the spec sets
container:, warn (or refuse) and point to[tool.lightcone.image]inpyproject.toml. It may also be worth raising with astra-spec / astra-tools whether the examples should still use the field.