New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on loading container details: invalid type string "SIGTERM", expected u64 #789
Comments
I was in the process of submitting a bug report as well. I have so far never came across an issue using Pods on Fedora Workstation, but after a recent Arch install, any container instance created with or without Pods always throws this toast message:
Similarly, inspecting the container yields:
Due to this, the 'size' field is blank and loads indefinitely, and the 'Inspection' utility cannot be entered. Also, I'm not sure if this is related in any way, but the only SIGTERM that appears in the container inspection is:
Environment
|
Maybe this is 2.0.1 on arch thing? |
It seems, Podman 5 had a breaking API change. So, serde can't deserialize the HTTP response. I'm thinking about to change to something like flexbuffers in order to handle such breakages easier. Also, https://github.com/vv9k/podman-api-rs seems to be unmaintained. |
Looks like there are a few people requesting podman-api-rs gains support for the 5.0 api: I'm dealing with another breaking change in the Podman 5.0 API, which is preventing pods from displaying containers correctly: For me, this is causing the following error:
Running the following command: I found that column 5702 was the colon in between:
|
The error appears when:
Opening "Containers" tab > Clicking on ANY kind of containers
I tried creating container from command-line, from the gui, tried different images, the error still appears each time consistently.
Pods version: 2.0.1 (flatpak)
The text was updated successfully, but these errors were encountered: