You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to log in to DockerHub with podman, I am getting:
$ podman login
Error: no registries found in registries.conf, a registry must be provided
So I have to login explicitly with:
$ podman login docker.io
of with:
podman login -u user -p pass -v docker.io
The same situation is with pulling a custom docker image:
$ podman pull epamedp/codebase-operator
Error: short-name "epamedp/codebase-operator" did not resolve to an alias and no unqualified-search registries are defined in "/home/user/.config/containers/registries.conf"
And again I have to indicate the registry explicitly:
$ podman pull docker.io/epamedp/codebase-operator
Could you help with this configuration?
P.S. Also, according to the article, it is advisable to indicate docker.io/library as a registry prefix and I also did not figure out how to do it.
I tried to modify /etc/containers/registries.conf as well. Still, the same issue.
I am using:
$ podman --version
podman version 3.4.4
The text was updated successfully, but these errors were encountered:
How to integrate
podman
withdocker.io
by default?According to these articles:
https://www.mankier.com/5/containers-registries.conf
https://www.redhat.com/sysadmin/manage-container-registries
you can configure a default registry by adding the file
$HOME/.config/containers/registries.conf
.I added this file and filled it out with these details:
When I try to log in to DockerHub with
podman
, I am getting:So I have to login explicitly with:
of with:
The same situation is with pulling a custom docker image:
And again I have to indicate the registry explicitly:
Could you help with this configuration?
P.S. Also, according to the article, it is advisable to indicate
docker.io/library
as a registryprefix
and I also did not figure out how to do it.I tried to modify
/etc/containers/registries.conf
as well. Still, the same issue.I am using:
The text was updated successfully, but these errors were encountered: