-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 API service returns incorrect JSON (missing Mounts
value) for Container List call
#12734
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 3, 2022
We are hard coding mounts to return nil in compat API, since we have the data, we should return it. Fixes: containers#12734 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 3, 2022
We are hard coding mounts to return nil in compat API, since we have the data, we should return it. Fixes: containers#12734 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 3, 2022
We are hard coding mounts to return nil in compat API, since we have the data, we should return it. Fixes: containers#12734 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Being fixed in #12735 |
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 4, 2022
We are hard coding mounts to return nil in compat API, since we have the data, we should return it. Fixes: containers#12734 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 4, 2022
We are hard coding mounts to return nil in compat API, since we have the data, we should return it. Fixes: containers#12734 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 21, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
The Podman API service returns incorrect JSON for a Docker Container List call: specifically, the
Mounts
property isnull
but should be populated with an object representing any mountpoints.Steps to reproduce the issue:
Launch a Podman container i.e.
podman run --name test -v /opt:/opt alpine:latest ash -c 'sleep infinity'
Launch the Podman API service i.e.
podman system service --time=0 unix:///tmp/podman.sock
Call the Docker Container List API i.e.
curl -s --unix-socket /tmp/podman.sock -H "Content-Type: application/json" -X GET "http:/v1.40/containers/json?all=true"
Launch an equivalent Docker container i.e.
docker run --name test -v /opt:/opt alpine:latest ash -c 'sleep infinity'
Call the Docker Container List API i.e.
curl -s --unix-socket /var/run/docker.sock -H "Content-Type: application/json" -X GET "http:/v1.40/containers/json?all=true"
Compare the results
Describe the results you received:
The Podman API returns JSON contains
"Mounts": null
.Describe the results you expected:
i.e.
(This value matches that returned by the Podman API for the Container Inspect call i.e.
curl -s --unix-socket /tmp/podman.sock -H "Content-Type: application/json" -X GET "http:/v1.40/containers/test/json"
).Additional information you deem important (e.g. issue happens only occasionally):
Happens consistently.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes. I'm running Debian Sid version 3.4.4, which matches the latest release. The issue also affected Podman 3.0.1 in Debian Bullseye.
I've checked the troubleshooting guide.
Additional environment details (AWS, VirtualBox, physical, etc.):
Running vanilla Debian Bullseye on a KVM VM with Debian Sid Podman v3.4.4.
The text was updated successfully, but these errors were encountered: