A copy of the system sudoers file that I placed into /etc/sudoers.d created an infinite include loop that broke sudo, and with no root login the VM seemed locked out. The qemu guest agent I covered in the previous post, accessed through Proxmox, provided a way to edit the protected file and undo the mistake...
After trying to run a docker command on a new home server and hitting the “user is not in the sudoers file” error, I look up the incident report in the journalctl logs, then explain how to properly gain sudo access. Instead of hand-editing /etc/sudoers, I add my user to the sudo group with usermod, covering why visudo exists and why I prefer sudo over logging in as root...
