Use fully qualified search registry for docker image names
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 310
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
Small issue here. The fix would be to use a fully qualified docker image name.
In Ubuntu 22.04, I must modify /etc/containers/registry.conf to allow "docker.io" as an unqualified-search-registries to pull the containers. As this is not present in the default configuration for Podman, it added an additional step.
It would be preferable to list the fully qualified names to avoid any confusion pertaining to where containers should be sourced from.
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
Inspect the toolkit's container image references and compare them with the fully qualified registry behavior described for Podman and /etc/containers/registry.conf. Verify that the relevant images can be pulled without adding docker.io as an unqualified search registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100