Option to not do docker pull?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Thank you 🙇♀ for wanting to create a feature in this repository. Before you do, please ensure you are filing the issue in the right place. Issues should only be opened on if the issue relates to code in this repository.
- If you have found a security issue please submit it here
- If you have questions or issues with the service, writing workflows or actions, then please visit the GitHub Community Forum's Actions Board
- If you are having an issue or question about GitHub Actions then please contact customer support
If you have a feature request that is relevant to this repository, the runner, then please include the information below:
Describe the enhancement
If I have a local runner and a locally maintained docker image i.e. not stored on a repository, I would like to avoid the "docker pull" step, which then fails.
Code Snippet
name: Self Hosted Tests
on: [push]
jobs:
integration_tests:
runs-on: self-hosted
container:
image: python3.6:latest
steps:
- name: Checkout
uses: actions/checkout@v2
- name: What java version do we have
run: java -version
Additional information
The image python3.6:latest is in my self-hosted runner's docker images. It doesn't exist in DockerHub or any other repository, and I don't want it to, because it should only ever be run on my self-hosted runner.
NOTE: if the feature request has been agreed upon then the assignee will create an ADR. See docs/adrs/README.md
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
Start with the self-hosted runner's container-job handling and reproduce the workflow shown in the issue using a locally available image that is absent from Docker Hub. The work is done when an explicit option allows the job to use that local image without attempting docker pull, while normal image behavior remains unchanged; review docs/adrs/README.md for the repository's ADR process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100