Podman Conmon-v3
Go back to the list of events.
Before participating in this test event, please first read the Podman Conmon-v3 instructions (opens in a new tab) .
Before participating in this test event, please first read the Podman Conmon-v3 instructions (opens in a new tab) .
Conmon-v3, set up of conmon
| Username | Profile | conmon sanity | Comments |
|---|---|---|---|
| Optional details about your system (hardware specs, software configuration, etc) relevant for the current test day | |||
|
Felix Koch
|
Fedora Workstation 44; Kernel 7.2.9-200.fc44.x86_64 | Pass | |
|
Filip Poboril
|
Fedora 44 Cloud Edition, KVM/QEMU, Kernel 6.19.10-300.fc44.x86_64 | Pass | |
|
Leandro Abdallah
|
Fedora 44, KVM/QEMU VM, 4 vCPU, 8 GB RAM, 60 GB disk, Podman 6.1.3 + conmon-v3 3.0.0-dev | Pass [1] | [1] Completed the conmon-v3 sanity test successfully. Verified podman info shows /usr/bin/conmon-v3 (version 3.0.0-dev). Container started with unique name, logs showed START and STDERR, exec printed EXEC_OK. After stop, container state was "exited". Exit code propagation worked correctly (42). Interactive TTY accepted input, printed TTY_OK, and returned to host shell after exit. No unexpected behavior observed. |
|
Marek Simek
|
Fedora Linux 46 (Cloud Edition Prerelease, rawhide), 7.3.0-0.rc6.261009gaf32da41b032.55.fc46.aarch64 kernel, Virtualization.framework VM (Lima) with 4GiB RAM, 100GiB disk, 4 cores on MacOs 27.0.1 | Pass | |
|
Paolo Junior Angeloni
|
Lenovo ThinkPad T450 i7-5600U, Fedora-Everything-netinst-x86_64-Rawhide-20261013.n.0.iso with swaywm and swaywm-extended groups | Pass [1] | [1] all expected results passed correctly with `podman info --debug` at https://paste.centos.org/view/b39fecfb |
|
Rajesh Prashanth
|
Fedora Linux 44 (Server Edition, x86_64), 6.19.10-300.fc44.x86_64 kernel, KVM/QEMU virtual machine with 3.81 GiB RAM, 15 GiB disk, 2 vCPUs on a 12th Gen Intel Core i5-12400F host. | Pass | |
|
Veronika Miticka
|
Fedora Workstation 43; Kernel 7.1.13-100.fc43.x86_64 | Pass |
Conmon Test: Ensure conmon Is Configured
| Username | Profile | conmon exit | conmon log file | conmon stdin | conmon interactive | conmon exec_stop | conmon journald | Comments |
|---|---|---|---|---|---|---|---|---|
| Optional details about your system (hardware specs, software configuration, etc) relevant for the current test day | ||||||||
|
Filip Poboril
|
Fedora 44 Cloud Edition, KVM/QEMU, Kernel 6.19.10-300.fc44.x86_64 | Pass | ||||||
|
Filip Poboril
|
Fedora 44 Cloud Edition, KVM/QEMU, Kernel 6.19.10-300.fc44.x86_64 | Pass | ||||||
|
Filip Pobořil
|
Fedora 44 Cloud Edition, KVM/QEMU, Kernel 6.19.10-300.fc44.x86_64 | Pass | Pass | Pass | Pass | Pass [1] | Pass | [1] including optional steps, no issues |
|
Leandro Abdallah
|
Fedora 44, KVM/QEMU VM, 4 vCPU, 8 GB RAM, 60 GB disk, Podman 6.1.3 + conmon-v3 3.0.0-dev | Pass [1] | Pass [2] | Pass [3] | Pass [4] | Pass [5] | Pass [6] |
[1]
Completed the common exit test successfully. Ran `podman run --rm ... sh -c 'exit 42'` and the exit code was correctly propagated to the host shell as 42. No unexpected behavior observed.
[2] Completed the common log file test successfully. Started a container with `podman run -d ... sh -c 'echo START; echo STDERR >&2; exec sleep 300'`. Both stdout (START) and stderr (STDERR) were correctly captured and displayed by `podman logs`. No unexpected behavior observed. [3] Completed the common stdin test successfully. Verified stdin works both via pipe (echo "hello from stdin" | podman run -i ... cat) and interactively (podman run -i ... sh -c 'cat > /tmp/input.txt && cat /tmp/input.txt'), with Ctrl+D properly terminating input. No unexpected behavior observed. [4] Completed the common interactive test successfully. Ran `podman run --rm -it ... sh`, the interactive shell accepted input, printed TTY_OK on `echo TTY_OK`, and returned to the host terminal after `exit`. No unexpected behavior observed. [5] Completed the common exec_stop test successfully. Started a container in detached mode, ran `podman exec "$name" echo EXEC_OK` which printed EXEC_OK. Then `podman stop -t 2 "$name"` stopped the container (SIGKILL warning appeared as expected for sleep), `podman inspect` showed state "exited", and `podman rm` removed the container cleanly. No unexpected behavior observed. [6] Completed the common journald test successfully. Ran a container with `--log-driver=journald` and the output was correctly captured by journald. Verified with `journalctl --since "1 minute ago" | grep "mensagem para o journald"`. No unexpected behavior observed. |
|
Marek Simek
|
Fedora Linux 46 (Cloud Edition Prerelease, rawhide), 7.3.0-0.rc6.261009gaf32da41b032.55.fc46.aarch64 kernel, Virtualization.framework VM (Lima) with 4GiB RAM, 100GiB disk, 4 cores on MacOs 27.0.1 | Pass | Pass | Pass | Pass | Pass |
Pass
Pass [1] |
[1] All TCs including optional steps. |
|
Paolo Junior Angeloni
|
Lenovo ThinkPad T450 i7-5600U, Fedora-Everything-netinst-x86_64-Rawhide-20261013.n.0.iso with swaywm and swaywm-extended groups | Pass [1] | Pass [2] | Pass [3] | Pass [4] | Pass [5] | Pass [6] |
[1]
expected results passed correctly, including optional
[2] expected results passed correctly [3] expected results passed correctly [4] expected results passed correctly [5] expected results passed correctly, including optional [6] expected results passed correctly |
|
Rajesh Prashanth
|
Fedora Linux 44 (Server Edition, x86_64), 6.19.10-300.fc44.x86_64 kernel, KVM/QEMU virtual machine with 3.81 GiB RAM, 15 GiB disk, 2 vCPUs on a 12th Gen Intel Core i5-12400F host. | Pass | Pass | Pass | Pass | Pass | Pass | |
|
Veronika Miticka
|
Fedora Workstation 43; Kernel 7.1.13-100.fc43.x86_64 | Pass | Pass | Pass | Pass | Pass | Pass |