Hello, I have an issue starting a container in the background inside github actions. The image for the container was just built by the buildah action and is not yet pushed. The idea is to smoke-test the image before pushing to the repository. What I see is
podman run -d --name=searchd --rm -u 14:0 -p 9306:9306 --platform=linux/amd64 ghcr.io/3scale/searchd:porta Trying to pull ghcr.io/3scale/searchd:porta... Error: initializing source docker://ghcr.io/3scale/searchd:porta: reading manifest porta in ghcr.io/3scale/searchd: manifest unknown Error: Process completed with exit code 125.
You can see the full pipeline here: https://github.com/3scale/searchd/actions/runs/4147557472/jobs/7174577031 Thank you!
Hi Aleksandar, Thank you for reaching out! On Mon, Feb 13, 2023 at 8:34 PM Aleksandar Kostadinov <akostadi@redhat.com> wrote:
Hello, I have an issue starting a container in the background inside github actions.
The image for the container was just built by the buildah action and is not yet pushed.
The idea is to smoke-test the image before pushing to the repository.
What I see is
podman run -d --name=searchd --rm -u 14:0 -p 9306:9306 --platform=linux/amd64 ghcr.io/3scale/searchd:porta Trying to pull ghcr.io/3scale/searchd:porta... Error: initializing source docker://ghcr.io/3scale/searchd:porta: reading manifest porta in ghcr.io/3scale/searchd: manifest unknown Error: Process completed with exit code 125.
You can see the full pipeline here: https://github.com/3scale/searchd/actions/runs/4147557472/jobs/7174577031
Please open an issue on github.com/containers/podman with a reproducer. You may be hitting some form of https://github.com/containers/podman/issues/17063 but I'd need more data to be sure. Kind regards, Valentin
Thank you! _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
<...>
Please open an issue on github.com/containers/podman with a reproducer. You may be hitting some form of https://github.com/containers/podman/issues/17063 but I'd need more data to be sure.
I think it not related: https://github.com/containers/podman/issues/17503 In any case there is an additional issue that githubs `ubuntu:latest` runner seems to include an older `podman` version. So all bets seem to be off there. And I don't see a proper action to run containers in the workflow. Everything I find is about running services for the whole duration or run a command and exit. While I want to cycle test a few built containers. I found a workaround though - to run containers with the particular platform tags (e.g. `quay.io/3scale/searchd:branchlinuxarm64`) and *NOT* specify `--platform`. Seems to be working. But I've hit another issue - that a mapped port from the service container is not accessible by another container at the expected hostname `host.containers.internal`. Although such mapped port is accessible from the host. So now I'm trying to use `podman pod create -n mypod` and then run all containers in the same pod so they see each other on `localhost`. I think that github workflows use case needs some good love from the podman team. It's very painful to use them. Including lack of `--jobs` option for the buildah step (https://github.com/redhat-actions/buildah-build/issues/115). Thank you.
participants (3)
-
akostadi＠redhat.com -
Aleksandar Kostadinov
-
Valentin Rothberg