letsencrypt / letsencrypt/boulder
Move boulder-tools image from dockerhub to github container registry
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Now that we have other container images in the github registry, we should consolidate on just using the one.
Contributor guide
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 by locating the boulder-tools image configuration and the existing GitHub Container Registry image definitions. Trace where the Docker image is built, published, and referenced, then verify that boulder-tools uses the GitHub registry consistently instead of Docker Hub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100