What problem does it solve? Stock Proxmox VE refuses to snapshot or clone LXC containers that carry bind or device mounts: the GUI snapshot button is greyed out and pct clone fails with "unable to clone mountpoint 'mpN' (type bind)". This Skill guides installing, verifying, and operating pve-bindsnap, a Perl overlay that delegates to Proxmox's real snapshot and clone code so bind-mount containers can be snapshotted and cloned. ## Core Features & Use Cases - Install and verify the overlay: Run the idempotent install script on the Proxmox node, then confirm activation via journalctl or a Perl check of $APPLIED and $CLONE_APPLIED. - Control snapshot and clone behavior with markers: Use BINDSNAP-FORCE-RUNNING for running containers, BINDSNAP-UNSUPPORTED for untested pve-container builds, and BINDSNAP-EXCLUDE: mpN to keep managed volumes out of snapshots or bind mounts out of clones. - Handle the checksum guard: Diagnose TEST mode on untested builds, opt in once, run the test plan, and report checksums so the build joins the known-good list. - Use Case: You need scheduled snapshots of a container whose mp0 bind mount points at host storage. After installing pve-bindsnap and adding BINDSNAP-FORCE-RUNNING to the CT Notes, your scheduler snapshots it like any other container. ## Quick Start Ask the assistant to install pve-bindsnap on your Proxmox node and verify that snapshot and clone now work for your bind-mount container.
