Difference between revisions of "Podman volume ls"
Jump to navigation
Jump to search
(2 intermediate revisions by the same user not shown) | |||
Line 9: | Line 9: | ||
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available | WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available | ||
WARN[0000] For using systemd, you may need to login using an user session | WARN[0000] For using systemd, you may need to login using an user session | ||
− | WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1001` (possibly as root) | + | WARN[0000] Alternatively, you can enable lingering with: `[[loginctl enable-linger 1001]]` (possibly as root) |
WARN[0000] Falling back to --cgroup-manager=cgroupfs | WARN[0000] Falling back to --cgroup-manager=cgroupfs | ||
+ | DRIVER VOLUME NAME | ||
+ | local minikube | ||
+ | |||
+ | [[loginctl enable-linger 1001]] | ||
+ | |||
+ | [[podman volume]] ls | ||
DRIVER VOLUME NAME | DRIVER VOLUME NAME | ||
local minikube | local minikube |
Latest revision as of 14:45, 28 October 2022
This article is a Draft. Help us to complete it.
podman volume ls WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available WARN[0000] For using systemd, you may need to login using an user session WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1001` (possibly as root) WARN[0000] Falling back to --cgroup-manager=cgroupfs WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available WARN[0000] For using systemd, you may need to login using an user session WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1001` (possibly as root) WARN[0000] Falling back to --cgroup-manager=cgroupfs DRIVER VOLUME NAME local minikube
loginctl enable-linger 1001
podman volume ls DRIVER VOLUME NAME local minikube
Related terms[edit]
See also[edit]
Advertising: