microsoft
Podman - Add troubleshooting text for Docker daemon not started
When running with Podman in a rootless environment, the daemon configuration can get tricky. If we have a daemon failure and are able to somehow detect they are running podman (or not) we should show the following info steps to configure.
As a non-root user run:
systemctl --user enable podman.socket systemctl --user start podman.socket systemctl --user status podman.socket
export DOCKER_HOST=unix:///run/user/1000/podman/podman.sock
sudo -s export DOCKER_HOST=unix:///run/user/1000/podman/podman.sock exit
The other problem with rootless configurations is that the home drive is typically too small to unpack a container so you have to add a disk then mount to /home, grant permissions and then run restorecon -R -v $HOME/.local/share/containers.
