Difference between revisions of "Podman volume ls"

From wikieduonline
Jump to navigation Jump to search
Line 3: Line 3:
  
 
  podman volume ls
 
  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
  
  

Revision as of 14:43, 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


Related terms


See also

Advertising: