sudoedit  was unable to find a usable temporary directory in which
             to store its intermediate files.

       The “no new privileges” flag is set, which prevents sudo from running as
             root.
             sudo was run by a process that has the Linux “no  new  privileges”
             flag  is  set.  This causes the set‐user‐ID bit to be ignored when
             running an executable, which will prevent sudo  from  functioning.
             The  most likely cause for this is running sudo within a container
             that sets this flag.  Check the documentation to see if it is pos‐
             sible to configure the container such that the flag is not set.

       sudo must be owned by uid 0 and have the setuid bit set
             sudo was not run with root privileges.  The sudo binary  does  not
             have  the  correct  owner or permissions.  It must be owned by the
             root user and have the set‐user‐ID bit set.

       sudoedit is not supported on this platform
             It is only possible to run sudoedit on systems that  support  set‐
             ting the effective user‐ID.

       timed out reading password
             The  user  did not enter a password before the password timeout (5
             minutes by default) expired.

       you do not exist in the passwd database
             Your user‐ID does not appear in the system passwd database.

       you may not specify environment variables in edit mode
             It is only possible to specify environment variables when  running
             a command.  When editing a file, the editor is run with the user’s
             environment unmodified.

SEE ALSO
       su(1),  stat(2),  login_cap(3), passwd(5), sudo.conf(5), sudo_plugin(5),
       sudoers(5), sudoers_timestamp(5), sudoreplay(8), visudo(8)

HISTORY
       See    the    HISTORY.md    file    in     the     sudo     distribution
       (https://www.sudo.ws/about/history/) for a brief history of sudo.

AUTHORS
       Many people