[GH-ISSUE #40] Allow setting user per guest #9

Closed
opened 2026-02-26 18:43:10 +03:00 by kerem · 5 comments
Owner

Originally created by @Nathanwoodburn on GitHub (Oct 27, 2025).
Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/40

Originally assigned to: @devnullvoid on GitHub.

It would be nice to allow users to specify an override of the default user for 1 guest

I usually have my VMs with username nathan however the LXC containers usually have root and no user account. So if I have the user set to nathan it won't let me log into the LXC containers

Originally created by @Nathanwoodburn on GitHub (Oct 27, 2025). Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/40 Originally assigned to: @devnullvoid on GitHub. It would be nice to allow users to specify an override of the default user for 1 guest I usually have my VMs with username `nathan` however the LXC containers usually have `root` and no user account. So if I have the user set to nathan it won't let me log into the LXC containers
kerem 2026-02-26 18:43:10 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@devnullvoid commented on GitHub (Oct 27, 2025):

Hi @Nathanwoodburn,

Thanks for the issue! Let me clarify how pvetui currently works:

LXC containers:

  • pvetui SSHs to the Proxmox host using ssh_user
  • Then runs sudo pct enter <id> which logs you in as root automatically
  • The ssh_user setting doesn't affect the LXC guest login at all

QEMU VMs:

  • pvetui SSHs directly to the VM's IP using ssh_user

Can you clarify what error you're seeing? Are you:

  1. Getting an SSH error connecting to the Proxmox host itself?
  2. Wanting to automatically log in as nathan inside LXC containers (currently not possible - pct enter always gives root)?

If it's #2, you can run su - nathan after entering the container. If you want automatic per-guest username support, that would be a feature request.

Thanks!

<!-- gh-comment-id:3453654687 --> @devnullvoid commented on GitHub (Oct 27, 2025): Hi @Nathanwoodburn, Thanks for the issue! Let me clarify how pvetui currently works: **LXC containers:** - pvetui SSHs to the Proxmox host using `ssh_user` - Then runs `sudo pct enter <id>` which logs you in as root automatically - The `ssh_user` setting doesn't affect the LXC guest login at all **QEMU VMs:** - pvetui SSHs directly to the VM's IP using `ssh_user` Can you clarify what error you're seeing? Are you: 1. Getting an SSH error connecting to the Proxmox host itself? 2. Wanting to automatically log in as `nathan` inside LXC containers (currently not possible - `pct enter` always gives root)? If it's `#2`, you can run `su - nathan` after entering the container. If you want automatic per-guest username support, that would be a feature request. Thanks!
Author
Owner

@Nathanwoodburn commented on GitHub (Oct 27, 2025):

Oh I'm assuming it is then an issue connecting to the PVE host. In that case I can just add a new user to PVE and fix it

<!-- gh-comment-id:3453662390 --> @Nathanwoodburn commented on GitHub (Oct 27, 2025): Oh I'm assuming it is then an issue connecting to the PVE host. In that case I can just add a new user to PVE and fix it
Author
Owner

@devnullvoid commented on GitHub (Oct 27, 2025):

Exactly! That's how I have mine set up: with a user jon on each PVE host. You can also add sudoers rules for that user to prevent being prompted for password when running pct enter.

https://github.com/devnullvoid/pvetui#-tips

<!-- gh-comment-id:3453715612 --> @devnullvoid commented on GitHub (Oct 27, 2025): Exactly! That's how I have mine set up: with a user `jon` on each PVE host. You can also add sudoers rules for that user to prevent being prompted for password when running `pct enter`. https://github.com/devnullvoid/pvetui#-tips
Author
Owner

@Nathanwoodburn commented on GitHub (Oct 27, 2025):

That works except for this error now

lxc-attach: 104: ../src/lxc/seccomp.c: lxc_seccomp_load: 1275 Operation canceled - Error loading the seccomp policy
lxc-attach: 104: ../src/lxc/attach.c: do_attach: 1376 Failed to attach to container

But that is likely an issue with PVE not the TUI

<!-- gh-comment-id:3453729921 --> @Nathanwoodburn commented on GitHub (Oct 27, 2025): That works except for this error now ``` lxc-attach: 104: ../src/lxc/seccomp.c: lxc_seccomp_load: 1275 Operation canceled - Error loading the seccomp policy lxc-attach: 104: ../src/lxc/attach.c: do_attach: 1376 Failed to attach to container ``` But that is likely an issue with PVE not the TUI
Author
Owner

@Nathanwoodburn commented on GitHub (Oct 27, 2025):

NVM looks like those are just broken LXC containers and my newer ones work fine

<!-- gh-comment-id:3453738962 --> @Nathanwoodburn commented on GitHub (Oct 27, 2025): NVM looks like those are just broken LXC containers and my newer ones work fine
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/pvetui#9
No description provided.