Hi Dan,

Thanks for reaching out.

On Fri, Mar 11, 2022 at 11:29 AM Dan via Podman <podman@lists.podman.io> wrote:

Hi all,

Recently I tried to run docker-compose with some example compose files and they all worked very nice. Great job! And thank you!

The only thing that I cannot run is https://github.com/mistio/mist-ce

After modifying image paths from "abc" to "docker.io/library/abc <http://docker.io/library/abc>" I can run docker-compose.yml with Podman 3.4.4 without errors and all containers that would normally run with Docker do run after docker-compose up -d. So it's difficult to say what went wrong...

If you look at the compose: https://github.com/mistio/mist-ce/releases/download/v4.6.2/docker-compose.yml

It's definitely complicated so it doesn't surprise me that something broke.

Has anyone tried please?

I haven't tried it yet but I have a suspicion. Podman resolves short names differently than Docker (see https://www.redhat.com/sysadmin/container-image-short-names). Prior to Podman v4.0, the Docker-compat REST API used the same mechanism of resolving short names Podman. Starting with Podman v4.0, short names of the Docker API will always resolve to docker.io.

What you can do is to either update to Podman v4.0 (see https://podman.io/blogs/2022/03/06/why_no_podman4_f35.html#using-podman4-copr) or changes /etc/containers/registries.conf to only use docker.io in the unqualified-search-registries.

The (fixed) bug in question: https://github.com/containers/podman/issues/12320

But I am only guessing and haven't tried running the compose file yet.

Kind regards,

Valentin

Thank you.

Kind regards,

Dan
_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io