-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
podman inspect returns Error: unexpected end of JSON input #22655
Comments
That's a very old Podman version. Upstream can only really support the latest version, so I can only recommend that you upgrade. If you have commercial support, you may want to open a case there. |
Hi, [root@overcloud-cephstorage-0 ~]# podman inspect 9a0ed16c31a654d6130fa0d146d5f14e3529a0eeb1eab1d28c8594f2b2cf0f5c [root@overcloud-cephstorage-0 ~]# podman info
[root@overcloud-cephstorage-0 ~]# [root@overcloud-cephstorage-0 ~]# podman version |
What distribution are you using that is shipping |
Also, we need details on the container that cannot be inspected. How was it created? Can it be deleted? Does this happen again if you delete + recreate? |
[root@overcloud-cephstorage-0 ~]# cat /etc/os-release It is a openstack setup, so i have a director node which acts as a local registry, it pulls image from quay.io/tripleomaster and stores it locally, which is then pulled by this particular and other systems from the director node. I have containers running already using this image so deleting the image would affect the running container which will then lead to outage in my infra. |
`[root@overcloud-cephstorage-0 ~]# yum provides podman podman-3.3.0-0.15.module_el8.5.0+870+f792de72.x86_64 : Manage Pods, Containers and Container Images podman-3.3.0-0.17.module_el8.5.0+874+6db8bee3.x86_64 : Manage Pods, Containers and Container Images podman-3.3.0-2.module_el8.5.0+877+1c30e0c9.x86_64 : Manage Pods, Containers and Container Images podman-3.3.0-4.module_el8.5.0+890+6b136101.x86_64 : Manage Pods, Containers and Container Images podman-3.3.0-8.module_el8.5.0+901+79ce9cba.x86_64 : Manage Pods, Containers and Container Images podman-3.3.1-3.module_el8.5.0+911+f19012f9.x86_64 : Manage Pods, Containers and Container Images podman-3.3.1-7.module_el8.5.0+914+45625a54.x86_64 : Manage Pods, Containers and Container Images podman-3.3.1-9.module_el8.6.0+938+04eb0c17.x86_64 : Manage Pods, Containers and Container Images podman-4.0.0-0.10.module_el8.6.0+944+d413f95e.x86_64 : Manage Pods, Containers and Container Images podman-1:3.4.1-3.module_el8.6.0+954+963caf36.x86_64 : Manage Pods, Containers and Container Images podman-2:4.0.2-1.module_el8.7.0+1106+45480ee0.x86_64 : Manage Pods, Containers and Container Images podman-2:4.2.0-1.module_el8.7.0+1196+721f4eb0.x86_64 : Manage Pods, Containers and Container Images podman-2:4.2.0-1.module_el8.7.0+1216+b022c01d.x86_64 : Manage Pods, Containers and Container Images podman-3:4.3.1-2.module_el8.8.0+1254+78119b6e.x86_64 : Manage Pods, Containers and Container Images podman-3:4.5.1-5.module_el8+461+0c6b54ea.x86_64 : Manage Pods, Containers and Container Images podman-3:4.6.0-1.module_el8+567+36ff2357.x86_64 : Manage Pods, Containers and Container Images podman-3:4.6.1-1.module_el8+643+8db347f4.x86_64 : Manage Pods, Containers and Container Images podman-3:4.6.1-2.module_el8+653+feef7bfe.x86_64 : Manage Pods, Containers and Container Images podman-3:4.6.1-4.module_el8+664+4072b3ae.x86_64 : Manage Pods, Containers and Container Images podman-3:4.6.1-5.module_el8+712+4cd1bd69.x86_64 : Manage Pods, Containers and Container Images podman-3:4.8.3-1.module_el8+804+f131391c.x86_64 : Manage Pods, Containers and Container Images podman-3:4.9.2-1.module_el8+899+3d7192e3.x86_64 : Manage Pods, Containers and Container Images podman-3:4.9.4-0.1.module_el8+971+3d3df00d.x86_64 : Manage Pods, Containers and Container Images podman-3:4.9.4-0.1.module_el8+971+3d3df00d.x86_64 : Manage Pods, Containers and Container Images ` |
These are the errors i am getting during deployment:
|
Without the Podman command used to create the container, our ability to help is strictly limited. |
But, we are not creating the container in this case. The container using this image is already running. What we are trying to do: So we take the signature and run an podman inspect 9a0ed16c31a654d6130fa0d146d5f14e3529a0eeb1eab1d28c8594f2b2cf0f5c, which gives us the error we are getting. |
sounds like you storage is corrupted, can you remove the image? Do other images work? |
Issue Description
[root@overcloud-cephstorage-0 ~]# podman version
Version: 3.4.1-dev
API Version: 3.4.1-dev
Go Version: go1.16.7
Built: Tue Oct 19 16:11:42 2021
OS/Arch: linux/amd64
So i have a image registry hosted in a server having ip 172.25.201.68 on port 8787, i had pulled 2 images earlier and everything was working fine, then i ran the pull again and now when inspecting one of the images i get Error: unexpected end of JSON input, but for others the podman inspect is working fine. I do not see this error in some of the machines for the same image, but i see this error on few machines with the same image.
[root@overcloud-cephstorage-0 ~]# podman pull 172.25.201.68:8787/tripleomaster/openstack-cron:current-tripleo Trying to pull 172.25.201.68:8787/tripleomaster/openstack-cron:current-tripleo... Getting image source signatures Copying blob dc0deb7c6c28 skipped: already exists Copying blob 1615f362c3b9 skipped: already exists Copying blob a3ed95caeb02 done Copying blob a3ed95caeb02 done Copying blob a3ed95caeb02 done Copying blob a3ed95caeb02 done Copying blob a3ed95caeb02 done Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Copying blob 788f94ed5eb6 skipped: already exists Copying blob e2cbf3fc8258 skipped: already exists Copying blob a3ed95caeb02 skipped: already exists Writing manifest to image destination Storing signatures 9a0ed16c31a654d6130fa0d146d5f14e3529a0eeb1eab1d28c8594f2b2cf0f5c [root@overcloud-cephstorage-0 ~]# [root@overcloud-cephstorage-0 ~]# podman inspect 9a0ed16c31a654d6130fa0d146d5f14e3529a0eeb1eab1d28c8594f2b2cf0f5c Error: unexpected end of JSON input
Whereas the same image is working on a different node:
[root@overcloud-controller-0 ~]# podman inspect 9a0ed16c31a654d6130fa0d146d5f14e3529a0eeb1eab1d28c8594f2b2cf0f5c [ { "Id": "9a0ed16c31a654d6130fa0d146d5f14e3529a0eeb1eab1d28c8594f2b2cf0f5c", "Digest": "sha256:de2f5e94491ebf5702cf7e1cefbce4643e0f42005cc210d817c0521c2b3effaf", "RepoTags": [ "172.25.201.68:8787/tripleomaster/openstack-cron:current-tripleo" ], "RepoDigests": [ "172.25.201.68:8787/tripleomaster/openstack-cron@sha256:9f5c53d6342200114593f63fe4e1321596bb9b45861abcdcb454fd3fbaae3a6f", "172.25.201.68:8787/tripleomaster/openstack-cron@sha256:de2f5e94491ebf5702cf7e1cefbce4643e0f42005cc210d817c0521c2b3effaf" ], "Parent": "", "Comment": "", "Created": "2022-02-09T05:23:45.932319128Z", ...
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
i got Error: unexpected end of JSON input when i tried to inspect the image
Describe the results you expected
podman inspect should work without any errors
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
this is a tripleo openstack setup
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: