docs: add Proxmox unprivileged LXC troubleshooting section#94
Open
otavio wants to merge 1 commit into
Open
Conversation
Document why SSH sessions disconnect immediately when the agent runs in an unprivileged Proxmox LXC container, split by agent type: devpts/fstab and PTY-limit fixes for the standalone agent, and the nesting/keyctl features plus the privileged-LXC-or-VM recommendation for the Docker agent. Ref: shellhub-io/shellhub#4634
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a troubleshooting section to the self-hosted docs for the common case of
the ShellHub agent running inside an unprivileged Proxmox LXC container, where
SSH sessions disconnect immediately after authentication.
Why
Recurring user reports (see shellhub-io/shellhub#4634). The failure looks like a
ShellHub bug but is rooted in how unprivileged LXC restricts PTY allocation and
host-namespace access. The guidance differs by agent type, which wasn't
documented anywhere.
Changes
in a Proxmox unprivileged LXC" entry, split into:
devpts//dev/shmentries from thecontainer
/etc/fstab, verify/dev/ptmxpermissions, and raiselxc.pty.maxif needed.features: nesting=1,keyctl=1to run Docker-in-LXC, andan honest recommendation to use a privileged container or a VM for the
host-namespace entry an unprivileged container cannot grant.
ns/timeline is cosmetic for the standalone case, and acaution that a privileged LXC is not a security boundary.
The companion agent fixes are in shellhub-io/shellhub#6458.