Description of problem: executing podman images --format '{{.ID}} {{printf "%12.12s %8s" .CreatedSince .Size}} {{$e:=""}}{{range $e = split .Repository "/"}}{{end}}{{$e}}:{{.Tag}}' crashes with core dump Version-Release number of selected component (if applicable): $ uname -a Linux localhost.localdomain 5.7.7-200.fc32.x86_64 #1 SMP Wed Jul 1 19:53:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ podman version Version: 2.0.2 API Version: 1 Go Version: go1.14.3 Built: Thu Jan 1 02:00:00 1970 OS/Arch: linux/amd64 How reproducible: crashes always Steps to Reproduce: 1. execute podman images --format '{{.ID}} {{printf "%12.12s %8s" .CreatedSince .Size}} {{$e:=""}}{{range $e = split .Repository "/"}}{{end}}{{$e}}:{{.Tag}}' Actual results: ... zsh: abort (core dumped) podman images --format Expected results: 831691599b88 3 weeks ago 223 MB centos:8 2a8d315e6208 8 weeks ago 208 MB fedora:32 a3282b72a167 3 months ago 76.2 MB ubuntu:20.04 08d05d1d5859 8 months ago 212 MB centos:7.7.1908 48650444e419 16 months ag 202 MB centos:6.10 Additional info: Worked on Fedora 32 with podman version Version: 1.9.3 RemoteAPI Version: 1 Go Version: go1.14.2 OS/Arch: linux/amd64 I've seen this 'split' not work on some ubuntu 19.10 environments w/ some podman installations (the "opensuse" version) -- withouth crashing though), but on fedora machines the podman images command line has always worked ('.CreatedSince', used to be '.Created' IIRC, but that is kinda irrelevant here)
This no longer crashes, that was fixed in some podman 2.0.x version. Now podman just outputs message: Error: template: list:1: function "split" not defined (and returns -1 to the parent process as I get error message "zsh: exit 125 podman images --format") I am fine to close this ticket, if I get some understanding why function 'split' used to work in previous podman versions (up to 1.9...) and it is no longer... I am also interested what functions are supported now (in addition to printf), if any (tried to find docs, tried to understand code, with no luck)
Does this command work on Docker?
I'll test shortly on systems I find docker (still) available, some mine, some friends/colleaques...
It works...: macOS Catalina 10.15.4% docker --version Docker version 19.03.12, build 48a66213fe macOS Catalina 10.15.4% docker images --format='{{$e:=""}}{{range $e = split .Repository "/"}}{{end}}{{$e}}:{{.Tag}}' container-image:latest macOS Catalina 10.15.4% docker images REPOSITORY TAG IMAGE ID CREATED SIZE hqxsr-cmmaven2:5000/container-image latest 18d4b56854a2 2 weeks ago 1.46GB
Jon could you take a look at this bug?
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Updated (Fedora) version from '32' to '34' in this bug report The problem still persists, and (IIRC) this is "upstream bugzilla" for this software fedora34$ podman --version podman version 3.1.2 fedora34$ podman images --format '{{.ID}} {{printf "%12.12s %8s" .CreatedSince .Size}} {{$e:=""}}{{range $e = split .Repository "/"}}{{end}}{{$e}}:{{.Tag}}' Error: template: list:1: function "split" not defined zsh: exit 125 podman images --format
Fixed in: * https://github.com/containers/common/pull/624 * https://github.com/containers/podman/pull/10688
As noted by Jhon, fixed in the PRs noted in https://bugzilla.redhat.com/show_bug.cgi?id=1855983#c8. This will be delivered in Podman 3.3 which is slated for RHEL 8.5 Assigning to Jindrich for any Packaging/BZ needs.
FEDORA-2021-d70c53ec97 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d70c53ec97
FEDORA-2021-d70c53ec97 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d70c53ec97` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d70c53ec97 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
podman images --format='{{$e:=""}}{{range $e = split .Repository "/"}}{{end}}{{$e}}:{{.Tag}}' worked for me as expected, with podman-3.3.0-0.2.rc1.fc34.x86_64
The change is interesting -- does that mean there was real bug which this attempt revealed, instead of a feature which happened to be there as a side effect?
@jhonce Do you have an answer to Tomi's question in https://bugzilla.redhat.com/show_bug.cgi?id=1855983#c13
As issues and bugs are reported we work on our docker compatibility. There were changes in some podman sub-commands where they were not using our containers/common report package. That could explain this change.
FEDORA-2021-94cbb4fa81 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-94cbb4fa81` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-94cbb4fa81 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-140dfde78f has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-140dfde78f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-140dfde78f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-7ce1dbeb75 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-7ce1dbeb75` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-7ce1dbeb75 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-7ce1dbeb75 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.