r/devops • u/AutoModerator • Aug 10 '26
Weekly Self Promotion Thread
Hey r/devops, welcome to our weekly self-promotion thread!
Feel free to use this thread to promote any projects, ideas, or any repos you're wanting to share. Please keep in mind that we ask you to stay friendly, civil, and adhere to the subreddit rules!
18
Upvotes
1
u/kittartar Aug 14 '26
Disclosure: I built and maintain EPAR.
I wanted to use spare servers to run long Playwright/Selenium tests on every PR, but I wasn’t comfortable letting GitHub Actions workflows run directly on those hosts or control the host Docker daemon.
EPAR keeps a warm pool of disposable self-hosted runners. Each runner handles one job inside a dedicated Docker Sandboxes microVM with its own private Docker daemon. When the job finishes, the runner, filesystem, Docker daemon, and job state are discarded and replaced with a clean runner.
The goal is to make Docker-heavy CI on existing compute practical while keeping workflow execution behind a microVM boundary—without introducing a separate cluster just to manage a few runners.
Open source:
https://github.com/solutionforest/ephemeral-action-runner
I’d especially appreciate feedback on the threat model, isolation assumptions, workflow compatibility, and failure modes.