Security Hardening and Docker Sandboxes - #12
Closed
joecklau wants to merge 11 commits into
Closed
Conversation
- register Docker Sandboxes as the default provider with wizard, templates, policy, and validation - separate provider integration, common pool lifecycle, image management, durable state, and storage responsibilities - add capacity admission, owned-artifact inventory, status and prune previews, bounded retention, and exact cleanup - preserve source and no-Go startup entry points with human-readable storage remediation - align configuration, development guidance, provider documentation, wrappers, and contract tests
Share guided Catthehacker image onboarding and source-aware storage admission across Docker-capable providers. Build and import verified Docker Sandboxes templates through an EPAR-owned Buildx builder with operational host trust, durable receipts, wrapper parity, tests, and updated documentation.
Add a host-wide exact resource catalog and reconcile owned provider artifacts during startup. Stream verified Docker Sandboxes archives directly into the sandbox cache, track WSL and Tart activation, bound BuildKit and no-Go controller storage, and separate operational build trust from runner trust. Improve long-running build progress, lifecycle diagnostics, and supervisor cleanup so temporary provider and GitHub failures do not retire healthy runners.
Persist per-config freshness checks with a weekly 07:00 local default and add an explicit image update command. Resolve exact Actions runner assets, coordinate scheduled pool maintenance across providers, and update onboarding, status, tests, wrappers, examples, and documentation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Testing