fix(run): isolate containerd from service to prevent boltdb lock#79
Merged
Conversation
…th service ephemerd run was sharing the same data directory and named pipe as the running service, causing BoltDB to hang waiting for a write lock. Use a unique temp directory and (on Windows) a unique named pipe per run.
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
1 participant
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
ephemerd runwas hanging at "waiting for response from boltdb open" because it shared the same data directory and Windows named pipe as the running ephemerd service\.\pipe\ephemerd-run-<suffix>) so the run command's containerd doesn't conflict with the serviceNext steps
no match for platform in manifestbecause the runner defaults toghcr.io/actions/actions-runner:latest(Linux-only). Need a Windows Server Core image for native Windows job execution.