[pkg-go] Bug#978650: podman: please provide a default container registry for looking up short image names

[Reinhard Tartler]

Can you please try the podman version in experimental? I believe what you
describe (the shortnames) should work with version 2.2 just fine thanks to
the shortnames.conf file.

Also, what version of podman did you use in Fedora for this test?

-rt

On Tue, Dec 29, 2020 at 12:45 PM Antonio Terceiro <terceiro at debian.org>
wrote:

> Package: podman
> Version: 2.1.1+dfsg1-3
> Severity: wishlist
>
> When running stuff that was originally written for docker, image names
> will usually be provided in their short form, i.e. debian:10,
> fedora:rawhide. In the current state of the Debian packaging, those will
> fail like this:
>
> $ cat Containerfile
> FROM debian
> $ podman build -t foobar .
> STEP 1: FROM debian
> Error: error creating build container: (image name "debian" is a short
> name and no search registries are defined in
> /etc/containers/registries.conf): while pulling "debian" as
> "localhost/debian": Error initializing source
> docker://localhost/debian:latest: error pinging docker registry localhost:
> Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection
> refused
>
> On Fedora, on the other hand, this just works, because their
> registries.conf provides by default a list of as few registries
> registries where to look up unqualified image names:
>
> [terceiro at fedora tmp]$ grep -v '^#' /etc/containers/registries.conf
> unqualified-search-registries = ['registry.fedoraproject.org', '
> registry.access.redhat.com', 'registry.centos.org', 'docker.io']
>
> I don't think we want to include the fedora/redhat/centos registries,
> but we should include at least the docker.io registry, which is the _de
> facto_ standard in the container world at the moment. So can we please
> provide something like the line below by default in
> /etc/containers/registries.conf?
>
> unqualified-search-registries = ['docker.io']
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
> 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1,
> 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
> Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
> LANGUAGE=pt_BR:pt:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages podman depends on:
> ii  conmon                           2.0.20-1
> ii  containernetworking-plugins      0.8.7-1
> ii  crun                             0.15.1+dfsg-1
> ii  golang-github-containers-common  0.26.3+ds1-2
> ii  init-system-helpers              1.60
> ii  libc6                            2.31-6
> ii  libdevmapper1.02.1               2:1.02.173-1
> ii  libgpgme11                       1.14.0-1+b2
> ii  libseccomp2                      2.5.1-1
> ii  runc                             1.0.0~rc92+dfsg1-5
>
> Versions of packages podman recommends:
> ii  buildah         1.16.6+dfsg1-2
> ii  catatonit       0.1.5-2
> ii  fuse-overlayfs  1.2.0-1
> ii  slirp4netns     1.0.1-1
> ii  tini            0.19.0-1
> ii  uidmap          1:4.8.1-1
>
> Versions of packages podman suggests:
> pn  containers-storage  <none>
>
> -- no debconf information
>


-- 
regards,
    Reinhard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20201231/ea5c50ab/attachment.html>