You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello! I found a surprising behavior via use of the podman-exporter to report metrics.
In creating a pod via kube play, the pod is created fine, but the metrics endpoint is failing with 500:
curl -s localhost:5000/v5.2.5/libpod/containers/stats
Request Failed(Internal Server Error): cannot run top on container 0c72.. as it did not create a cgroup: this container does not have a cgroup
error logged:
GET /v5.2.5/libpod/containers/stats?all=false&interval=1&stream=false HTTP/1.1" 500 239 "" "Go-http-client/1.1"
Here the container 0c72.. is a pause container. I would not expect the endpoint to crash 500 and deny all stat info.
Notably podman is rootless mode and in k8s (ie like DnD). Not seeing the problem in native host mode.
Unclear if containers.conf is the source of problem. Have not had time to extensively rtfm there, but a latest attempt looked like this (largely inherited from /etc version found at https://quay.io/repository/containers/podman)
Issue Description
hello! I found a surprising behavior via use of the podman-exporter to report metrics.
In creating a pod via
kube play
, the pod is created fine, but the metrics endpoint is failing with 500:error logged:
Here the container
0c72..
is a pause container. I would not expect the endpoint to crash 500 and deny all stat info.Notably podman is rootless mode and in k8s (ie like DnD). Not seeing the problem in native host mode.
Unclear if
containers.conf
is the source of problem. Have not had time to extensively rtfm there, but a latest attempt looked like this (largely inherited from /etc version found at https://quay.io/repository/containers/podman)Version info
The text was updated successfully, but these errors were encountered: