Change order of containers initialization
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Describe the enhancement
Change the order in which job services and job container are started.
Currently the order is as follows:
- start job container
- start all job services
- wait until all job services are ready
The proposal is to change the order to the following:
- start all job services
- wait until all job services are ready
- start job container
it makes more sense to start job container after all the services are started, as the job container might use services already in an early stage.
The actual need for this change arose from this request https://github.com/actions/virtual-environments/issues/2095
Long story short: it is desired to use services to initialize qemu and binfmt-support before the actual job container is started.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Trace the runner's job-service and job-container startup path, then verify that services start and become ready before the job container, including the qemu and binfmt-support use case described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100