opensafely-core / opensafely-core/opensafely-cli
Stale docker auth config prevents pulling new images
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 5
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 4
Description
$ opensafely pull
Updating OpenSAFELY cohortextractor image
Error response from daemon: Head "https://ghcr.io/v2/opensafely-core/cohortextractor/manifests/latest": denied: denied
I was able to fix this by running docker logout ghcr.io, which has removed a section from ~/.docker/config.json.
See this Slack thread.
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 by reproducing opensafely pull with the stale ~/.docker/config.json entry and compare the behavior after docker logout ghcr.io. Trace the opensafely pull entry point to determine how Docker authentication is handled; done means new images can be pulled without requiring users to log out manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100