Image: ghcr.io/farizgd/node24-fariz-fix:latest
This image uses the upstream Termux PRoot-Distro Python CLI on a regular Debian host, not Termux and not a handwritten proot -r invocation. The Docker container still runs as an unprivileged user. It does not grant real root or kernel capabilities.
On first start, the image imports its prebuilt Debian Trixie + Node.js 24 tarball using proot-distro install ... --name node24. It then starts the guest with proot-distro login node24. The installation and future apt changes persist under the container user's home directory, which Pterodactyl mounts at /home/container.
Important migration note: Existing /home/container/.proot-debian from the old image is left untouched. PRoot-Distro has a different container layout, so this creates a fresh guest. Back up files in the old rootfs and copy any required files/configuration into the new guest manually. The Pterodactyl home directory is bind-mounted and remains accessible inside the guest. Do not delete .proot-debian until you have migrated what you need.
The default console opens interactive Bash. The egg's STARTUP is ignored by default. Set PROOT_USE_STARTUP=1 to execute the egg STARTUP within Debian. Explicit Docker command arguments also execute within Debian.
After CI publishes a new image, select ghcr.io/farizgd/node24-fariz-fix:latest in your panel and restart the container so Wings pulls it.
Try inside the console:
whoami
node -v
apt update
apt install -y fastfetch
fastfetchPRoot-Distro CLI is on the outer Docker host environment, not installed inside the nested guest. The host has the CLI in /opt/proot-distro-venv/bin/proot-distro. Use the panel's normal startup to enter the guest. This is still rootless: package post-install scripts that demand real kernel capabilities or privileged mounts may fail, including some OpenSSH configurations.
The node must allow PRoot ptrace operations. The image supports amd64/arm64 depending on the CI build. Existing GitHub Actions build/test workflow should be reviewed for old .proot-debian assumptions and updated before relying on green CI.
The image uses Debian Dropbear on TCP port 26006, started automatically from the persistent Debian guest. This avoids OpenSSH's pre-auth chroot failure under rootless PRoot. The Pterodactyl allocation and upstream firewall must allow TCP/26006.
For the existing persistent guest, the root password you already set with passwd root is preserved. If you want to set or rotate it across future restarts, run this in the Pterodactyl guest console:
read -r -s -p 'New root password: ' pw; echo; printf '%s\\n' "$pw" > /home/container/.ssh-root-password; chmod 600 /home/container/.ssh-root-password; printf 'root:%s\\n' "$pw" | chpasswd; unset pwThis stores the password privately under the Pterodactyl persistent volume, not in GitHub. On startup, the script reapplies it when present. If the root account is locked and no password file exists, set a password first. For logs use cat /home/container/ssh.log.
Dropbear does not require OpenSSH Server's patched .deb. Public key authentication is not explicitly disabled in this release; root password authentication is enabled. Use a strong unique password and ideally limit access to trusted IPs.