Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Podman - Add troubleshooting text for Docker daemon not started

Open
#488 0 comments 0 reactions 1 assignee View on GitHub

@stuartpa is already working on this.

Since Dec 7, 2023.

Assessment

This issue has not been assessed yet.

Description

bug documentation

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.

Dominant language
Go
Stars
595
Forks
91
Avg merge
9h 35m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/go-sqlcmd

All issues in microsoft/go-sqlcmd

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.