infra-proxmox-bindsnaplisted

# proxmox-bindsnap Install, verify, configure and operate **pve-bindsnap** -- a small Perl overlay that lets Proxmox snapshot AND clone LXC containers that carry bind/device mounts (`mpN` pointing at host paths), which stock Proxmox greys out or refuses with `unable to clone mountpoint 'mp0' (type bind)`. It delegates to Proxmox's real snapshot/clone code (it does not fork it) by dpkg-diverting `PVE::LXC::Config` (snapshots) and `PVE::API2::LXC` (clone). Source: https://github.com/bitranox/pve-bindsnap **Run on the Proxmox VE node, as root.** If you are driving the node from elsewhere, prefix each command with `ssh root@<node>`. All `pct`/`journalctl`/`perl` commands below run on the node. ## When to use - A container with a bind mount can't be snapshotted (the GUI button is greyed out). - `pct clone` / GUI Clone fails: `unable to clone mountpoint 'mpN' (type bind)`. - You need scheduled snapshots of bind-mount CTs (e.g. cv4pve-autosnap). - You want to clone a bind-mount CT and control whether the copy inherits the bind mounts. **Not for:** containers without bind/device mounts (they already snapshot/clone stock -- the overlay never touches them). If you only need a rootfs snapshot and not the GUI/scheduler, plain `zfs snapshot <pool>/subvol-<vmid>-disk-0@name` on the stopped CT is simpler and needs none of this. ## 1. Install The model is "read the source, then install from it." Inspect first: ``` curl -fsSL https://raw.githubusercontent.com/bitranox/pve-bindsnap/mai