-
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
MacOS - podman container stats is failing with missing cgroups v2
#11909
Labels
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
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.
remote
Problem is in podman-remote
Comments
mheon
added
kind/bug
Categorizes issue or PR as related to a bug.
remote
Problem is in podman-remote
labels
Oct 11, 2021
@jwhonce PTAL |
I think the check for unified and rootless needs to be moved away from client to backend. |
I take this one. |
Luap99
added
the
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
label
Oct 11, 2021
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Oct 11, 2021
Podman state is not supported for rootless cgroupv1 setups. The check for this must be on the server side and not the client. Fixes containers#11909 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Oct 11, 2021
Podman stats is not supported for rootless cgroupv1 setups. The check for this must be on the server side and not the client. Fixes containers#11909 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Oct 11, 2021
Podman stats is not supported for rootless cgroupv1 setups. The check for this must be on the server side and not the client. [NO NEW TESTS NEEDED] we cannot test this because remote and server are always on the same machine in CI Fixes containers#11909 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Oct 19, 2021
Podman stats is not supported for rootless cgroupv1 setups. The check for this must be on the server side and not the client. [NO NEW TESTS NEEDED] we cannot test this because remote and server are always on the same machine in CI Fixes containers#11909 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Oct 19, 2021
Podman stats is not supported for rootless cgroupv1 setups. The check for this must be on the server side and not the client. [NO NEW TESTS NEEDED] we cannot test this because remote and server are always on the same machine in CI Fixes containers#11909 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Nov 12, 2021
Podman stats is not supported for rootless cgroupv1 setups. The check for this must be on the server side and not the client. [NO NEW TESTS NEEDED] we cannot test this because remote and server are always on the same machine in CI Fixes containers#11909 Signed-off-by: Paul Holzinger <pholzing@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
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
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.
remote
Problem is in podman-remote
Context
podman container stats ID
ends withError: stats is not supported in rootless mode without cgroups v2
But
podman machine ssh podman container stats
Works without an issue, command is missing a remote check.
The text was updated successfully, but these errors were encountered: