podman @4.8.2: Error: preparing container when running podman, conmon 2.1.9's problem

[AntonioSun]

$ podman run --rm -it debian:stable-backports echo "Hello"
Writing manifest to image destination
Error: preparing container 09...9e for attach: container create failed (no logs from conmon): conmon bytes "": readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...

$ port installed requested | grep conmon | wc
      0       0       0

$ podman version
Client:       Podman Engine
Version:      4.8.2
API Version:  4.8.2
Go Version:   go1.21.5
Built:        Wed Dec 31 19:00:00 1969
OS/Arch:      darwin/arm64

Server:       Podman Engine
Version:      4.7.2
API Version:  4.7.2
Go Version:   go1.21.1
Built:        Tue Oct 31 10:30:33 2023

$ uname -srm
Darwin 23.1.0 arm64

$ sw_vers
ProductName:		macOS
ProductVersion:		14.1.2
BuildVersion:		23B92

It should be fixed upstream, ​https://github.com/containers/conmon/issues/475, but still exist under macports

[catap (Kirill A. Korinsky)]

You're using 4.8.2 version of podman client on your macOS from MacPorts, but the engine is older and has version 4.7.2. So, the bug should be fixed inside your engine by update the version.

You may login into it via podman machine ssh and update it, or recreate it from image which contains fresh podman.

[AntonioSun]

or recreate it from image which contains fresh podman

hmm..., if you meant podman machine rm then podman machine init, then I've tried it twice.

I'll give podman machine ssh a try...

[catap (Kirill A. Korinsky)]

Replying to AntonioSun:

or recreate it from image which contains fresh podman

hmm..., if you meant podman machine rm then podman machine init, then I've tried it twice.

I'll give podman machine ssh a try...

podman uses fedora based image by default and I've recreated machine few days ago and it was used fedora-coreos-39.20231204.2.1-qemu.x86_64.qcow2 as base image => recreating probably won't help yet.

[AntonioSun]

Would you publish your fedora-coreos-39.20231204.2.1-qemu.x86_64.qcow2 somewhere and how can I use it if you would please?

As I've tried to podman machine ssh to update it, doing it for the first time of my whole life, using google as helper in each step:

$ sudo dnf upgrade
sudo: dnf: command not found

$ sudo yum check-update
sudo: yum: command not found

$ sudo rpm-ostree upgrade
No upgrade available.

I.e., all my attempts failed, and I have no further ideas how to proceed. please help. thx.

UPDATE:

PS -- Is your Mac intel based? Why it is of x86_64 architecture, instead of arm64? thx

[catap (Kirill A. Korinsky)]

Replying to AntonioSun:

I.e., all my attempts failed, and I have no further ideas how to proceed. please help. thx.

With assumption that your image is based on fedora coreos as mine you may update it via rpm-ostree.

Anyway, it won't help because all streams are month old: ​https://fedoraproject.org/coreos/release-notes?arch=aarch64&stream=next and the next stream contains podman 4.7.2 :(

Interesting that the year before they hadn't have such huge delay in updates of the next stream, and I hope that in week or two it finally gets an update.

PS -- Is your Mac intel based? Why it is of x86_64 architecture, instead of arm64? thx

I'm using macOS 12 / x86_64 at laptop, I do have some test machines with arm64 and I was one of the first who started to work to support it by software but I still have a few blockers which prevents me to switch to it as daily laptop.

:)

[AntonioSun]

You're using 4.8.2 version of podman client on your macOS from MacPorts, but the engine is older and has version 4.7.2.

This morning when I tried it again, I'm pulling fedora-coreos-39.20240104.2.0-qemu.aarch64.qcow2.xz this time, and I've confirmed that everything is working now:

$ podman version
Client:       Podman Engine
Version:      4.8.2
API Version:  4.8.2
Go Version:   go1.21.5
Built:        Wed Dec 31 19:00:00 1969
OS/Arch:      darwin/arm64

Server:       Podman Engine
Version:      4.8.2
API Version:  4.8.2
Go Version:   go1.21.4
Built:        Mon Dec 11 08:22:43 2023
OS/Arch:      linux/arm64

$ podman run --rm -it debian:stable-backports echo "Hello"
Hello

The issue can be closed now. thanks everyone!

[judaew (Vadym-Valdis Yudaiev)]

It's great that the issue has disappeared. Thanks to Kirill for deeply understanding the issue.