Rootless errors

Rootless-mode errors are specific to user-namespace, capability, session, and kernel configuration required for non-root operation.

These pages help users compare related error messages, common causes, and how-to-fix steps across different tools that fail in the same way.

Rootless-mode errors usually affect more advanced setups, but the users searching them often need very concrete guidance because the failure depends on kernel capabilities, user namespaces, session state, or host policy.

This hub groups rootless operation errors into one place so users can troubleshoot privilege boundaries and non-root runtime assumptions with less guesswork.

Docker

Back to all categories

cannot expose privileged port

Docker rootless mode could not publish a privileged portDocker

No subuid ranges found for user

Docker rootless mode could not set up UID or GID mappingDocker

failed to start the child: no space left on device

Docker rootless mode failed because max_user_namespaces is too smallDocker

failed to start the child: operation not permitted

Docker rootless mode failed to start because unprivileged user namespaces are disabledDocker

read unix @->/run/systemd/private: connection reset by peer

Docker rootless run failed because the user dbus daemon is not runningDocker