summaryrefslogtreecommitdiff
path: root/docs/source/markdown
diff options
context:
space:
mode:
authorAndrej Shadura <andrew.shadura@collabora.co.uk>2021-03-23 15:17:24 +0100
committerAndrej Shadura <andrew.shadura@collabora.co.uk>2021-04-27 11:20:43 +0200
commit09e640d1b5dbfaa47abb2ac2357ce8e96b108ae3 (patch)
treeddfce238810bcff5c67b2ab41ff054af16fe54e9 /docs/source/markdown
parent54344d3a6440f2e80b9eba5205e87b6b4261c02c (diff)
downloadpodman-09e640d1b5dbfaa47abb2ac2357ce8e96b108ae3.tar.gz
podman-09e640d1b5dbfaa47abb2ac2357ce8e96b108ae3.tar.bz2
podman-09e640d1b5dbfaa47abb2ac2357ce8e96b108ae3.zip
rootless: Tell the user what was led to the error, not just what it is
Users coming e.g. from Docker do not always read the manual and expect podman to not require sudo or uidmap, for them the default message is not very helpful: Error: Cannot connect to the Podman socket, make sure there is a Podman REST API service running.: cannot find newuidmap: exec: "newuidmap": executable file not found in $PATH Adding a bit more context to this would help to nudge them into the right direction and tell them what to look for in the documentation: command required for rootless mode with multiple IDs: exec: "newuidmap": executable file not found in $PATH Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk> [NO TESTS NEEDED]
Diffstat (limited to 'docs/source/markdown')
0 files changed, 0 insertions, 0 deletions