Andrej Shadura 09e640d1b5 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]		2021-04-27 11:20:43 +02:00
..
rootless.go	[NO TESTS NEEDED] Shrink the size of podman-remote	2021-03-29 09:49:45 -04:00
rootless_linux.c	Move socket activation check into init() and set global condition.	2021-04-05 17:43:11 +08:00
rootless_linux.go	rootless: Tell the user what was led to the error, not just what it is	2021-04-27 11:20:43 +02:00
rootless_test.go	rootless: automatically split userns ranges	2021-01-07 09:42:27 +01:00
rootless_unsupported.go	validate fds --preserve-fds	2020-08-04 15:09:17 -04:00