Re: Bug#978650: podman: please provide a default container registry for looking up short image names

[Reinhard Tartler <siretart@gmail.com>]

Context is what version of podman to ship in Debian bullseye

On Thu, Jan 14, 2021 at 11:29 AM Antonio Terceiro <terceiro@debian.org> wrote:

On Sat, Jan 09, 2021 at 12:58:05PM +0200, Faidon Liambotis wrote:
> Hi there,
>
> On Thu, Dec 31, 2020 at 01:39:52PM -0500, Reinhard Tartler wrote:
> > As I thought. Experimental has version 2.2, unstable/testing currently 2.1
> > What you are asking for is one (maybe the?) major new feature introduced in
> > 2.2.0.
>
> That's helpful! I was wondering what your plans were with regards to
> bringing 2.2 to unstable. With my limited testing, things look to work
> OK with it. It'd be great to release bullseye with a version supporting
> short names!

yes please :)

> Thank you for your efforts in maintaining the podman/libpod/etc. stack.

+1

 

You're welcome.

In the community meeting on Dec 1 (cf. https://podman.io/community/meeting/notes/2020-12-01/#brent-baude)

Brent Baude (with some clarifications from Dan Walsh, IIRC) stated that version 2.2

won't make it into any RHEL release. RHEL 8.3 will go with podman 2.1, whereas RHEL 8.4

will go straight with podman 3.0. podman 2.2 will only be in Fedora, and given the

development velocity and support burden for the podman team, I was hesitating with

committing on podman 2.2 for bullseye. That's not a hard no from my side, I'm happy

to hear other opinions.

One could be to let's go straight for podman 3.0. Since Debian is going to have a

hard-freeze on 2021-03-12, that's kind of tight, but if doable if we collaborate.

There are a couple of dependencies that we need to update in experimental and I would

really appreciate help with it.

So folks, what do you think?

--

regards,
    Reinhard