Eighteen hours to close the loop

Description and use

cidx in Lithair’s CI reused a previous container when the privileged flag changed, causing a permission error. After opening issue #531 and subsequent fixes, the hash was updated to include the privileged flag, ensuring the container is recreated. The issue was resolved in eighteen hours.

Problem

cidx reused a previously created container when the privileged flag changed, causing permission errors during CI runs.

Outcome

The issue was resolved within eighteen hours, demonstrating rapid issue triage and release cadence in the open‑source ecosystem.

Workflow

• Define CI container in cidx.toml with privileged=true
• Run CI job, container fails with permission error
• Open cidx issue #531
• Add privileged flag to container hash
• Open cidx issue #532 to recreate container when user changes
• Open cidx issue #533 to compare actual environment
• Release cidx v3.8.0 with fixes
• Update Lithair to use cidx v3.8.0
• Regenerate GitHub workflow with cidx generate github

Evidence

cidx reuses containers from one run to the next. To decide whether the existing container is still the right one, it hashes the configuration: image, command, working directory, entrypoint, volumes, environment variables.

Source

privileged = true is right there, read three times. The container still runs as the host user.

Source

cidx#531 opened: "privileged reuses the previous container"

Source

cidx#532 recreate the container when the user it runs as changes

Source