Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

proxmox-lxc

Étoiles0

Forks0

Mis à jour29 juin 2026 à 20:30

Manage Proxmox LXC containers via the REST API — list, inspect, start/stop, create, clone, migrate, snapshot, and basic config. Covers the privileged-vs-unprivileged distinction and where simple mount points end and host-file edits begin. Load this for LXC/container tasks on Proxmox. For lxc.idmap, bind-mount UID remapping, nesting/keyctl tweaks, or hookscripts, use proxmox-host-config.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Redth

Redth/homelab-assist

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	proxmox-lxc
description	Manage Proxmox LXC containers via the REST API — list, inspect, start/stop, create, clone, migrate, snapshot, and basic config. Covers the privileged-vs-unprivileged distinction and where simple mount points end and host-file edits begin. Load this for LXC/container tasks on Proxmox. For lxc.idmap, bind-mount UID remapping, nesting/keyctl tweaks, or hookscripts, use proxmox-host-config.

Proxmox LXC containers

Manage LXC (system containers) through the REST API (see proxmox-api). Obey the homelab-core:homelab-safety skill. Note: a "Docker host LXC" is a common homelab pattern — for how Docker interacts with LXC privilege/storage/VLAN, see docker:docker-on-proxmox.

Privileged vs unprivileged — know which you have

Unprivileged (default, recommended): container root (uid 0) is mapped to an unprivileged host uid (typically 100000+). Safer, but bind mounts and device access need UID/GID remapping (lxc.idmap) — a host-file edit, not an API call → proxmox-host-config.
Privileged: container root == host root. Simpler mounts/devices, but a container escape = host compromise. Avoid unless a workload truly needs it (and understand the risk).

Check: GET /nodes/{node}/lxc/{vmid}/config → look for unprivileged: 1.

Inspect (read-only)

scripts/pve-api.sh GET /nodes/{node}/lxc                              # list containers
scripts/pve-api.sh GET /nodes/{node}/lxc/{vmid}/status/current        # state
scripts/pve-api.sh GET /nodes/{node}/lxc/{vmid}/config                # config incl. mp0..mpN, net, features

Lifecycle (write — confirm first)

scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/status/start
scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/status/shutdown
scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/status/stop
scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/status/reboot

Snapshots

scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/snapshot --data 'snapname=pre-change'
scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/snapshot/{snap}/rollback   # destructive

Create / clone

scripts/pve-api.sh POST /nodes/{node}/lxc --data 'vmid=210&hostname=svc&ostemplate=local:vztmpl/debian-12-standard_amd64.tar.zst&memory=2048&cores=2&rootfs=local-lvm:8&net0=name=eth0,bridge=vmbr0,ip=dhcp&unprivileged=1'
scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/clone --data 'newid=211&hostname=svc2'

Verify template names (GET /nodes/{node}/storage/{store}/content) and field shapes against the API viewer for the running version.

Mount points — where API ends and host edits begin

Simple mount points can be set via config: mp0=local-lvm:8,mp=/data (a new volume) or a bind mount mp0=/host/path,mp=/data. The API can set these (POST .../config).
But on an unprivileged container, a host bind mount usually has the wrong ownership inside the container unless you set up lxc.idmap UID/GID remapping — that lives in /etc/pve/lxc/{vmid}.conf and is a host-file edit. Likewise features like nesting=1, keyctl=1, fuse=1 (needed for Docker-in-LXC) and any lxc.* raw keys or hookscripts. → use proxmox-host-config and confirm the SSH drop.

Network / VLAN

Basic NIC config (net0=name=eth0,bridge=vmbr0,tag=<vlan>,ip=dhcp) is settable via the API. The underlying VLAN-aware bridge and /etc/network/interfaces are host-level (proxmox-host-config). For the full Docker-host-in-LXC VLAN/storage picture, see docker:docker-on-proxmox.

Before you act

Check version, verify fields, snapshot before risky changes, summarize + get approval. For anything touching lxc.idmap, features, raw lxc.*, or hookscripts, route to proxmox-host-config.

Plus depuis ce dépôt

même dépôt

dockhand

Redth/homelab-assist

Manage Docker via Dockhand — the preferred control plane in this homelab — and its Hawser remote agents. Covers the Dockhand architecture (central server + Hawser Standard/Edge agents), how to drive it (the mcp-dockhand MCP server or its REST API), compose-stack and container operations, multi-host/environment targeting, and Git-synced stacks. Load this when the user manages Docker with Dockhand.

2026-07-010

docker-compose-stacks

Redth/homelab-assist

Shared foundational knowledge for working with Docker Compose stacks — the compose file format, services/networks/volumes/secrets, environment and .env handling, healthchecks, common operations (up/down/pull/logs/ps), and safe-change practices. Load this for any compose-based work, alongside the control-plane skill (Dockhand/Portainer/Dockge) that actually applies the changes.

2026-06-290

docker-on-proxmox

Redth/homelab-assist

Understand and troubleshoot a Docker host running inside Proxmox — as a VM or as a privileged/unprivileged LXC — and how VLAN networking, macvlan/ipvlan, VLAN-aware bridges, and passed-through/bind-mounted storage interact across the Proxmox and Docker layers. Load this when a Docker networking or storage problem may originate at the Proxmox layer, or when planning how to host Docker on Proxmox.

2026-06-290

docker-overview

Redth/homelab-assist

Entry point and router for managing Docker in a homelab. Load this first for any Docker request — it identifies which control plane is in use (Dockhand preferred, or Portainer/Dockge/raw Engine), establishes the version check, and routes to the right skill (compose stacks, Dockhand, reverse-proxy label routing, or Docker-on-Proxmox networking).

2026-06-290

dockge

Redth/homelab-assist

Manage Docker compose stacks via Dockge — a file-based stack manager that stores stacks as compose files under /opt/stacks. Covers its file-on-disk model, the lack of a REST API/MCP (so operations are filesystem- or SSH-oriented), and how to edit stacks safely. Load this when the user manages Docker with Dockge.

2026-06-290

npm-reverse-proxy

Redth/homelab-assist

Set up and manage domain routing for homelab services using nginx-proxy-manager (NPM) driven by Docker container labels via npm-docker-sync. Load this when the user wants to expose a container/stack at a domain, debug why a service isn't routing, or understand the label-based proxy-host automation pattern. Covers the npm.* label scheme, how sync maps containers to NPM proxy hosts, and SSL/forced-host details.

2026-06-290

name	proxmox-lxc
description	Manage Proxmox LXC containers via the REST API — list, inspect, start/stop, create, clone, migrate, snapshot, and basic config. Covers the privileged-vs-unprivileged distinction and where simple mount points end and host-file edits begin. Load this for LXC/container tasks on Proxmox. For lxc.idmap, bind-mount UID remapping, nesting/keyctl tweaks, or hookscripts, use proxmox-host-config.

Proxmox LXC containers

Privileged vs unprivileged — know which you have

Unprivileged (default, recommended): container root (uid 0) is mapped to an unprivileged host uid (typically 100000+). Safer, but bind mounts and device access need UID/GID remapping (lxc.idmap) — a host-file edit, not an API call → proxmox-host-config.
Privileged: container root == host root. Simpler mounts/devices, but a container escape = host compromise. Avoid unless a workload truly needs it (and understand the risk).

Check: GET /nodes/{node}/lxc/{vmid}/config → look for unprivileged: 1.

Inspect (read-only)

scripts/pve-api.sh GET /nodes/{node}/lxc                              # list containers
scripts/pve-api.sh GET /nodes/{node}/lxc/{vmid}/status/current        # state
scripts/pve-api.sh GET /nodes/{node}/lxc/{vmid}/config                # config incl. mp0..mpN, net, features

Lifecycle (write — confirm first)

scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/status/start
scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/status/shutdown
scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/status/stop
scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/status/reboot

Snapshots

scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/snapshot --data 'snapname=pre-change'
scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/snapshot/{snap}/rollback   # destructive

Create / clone

scripts/pve-api.sh POST /nodes/{node}/lxc --data 'vmid=210&hostname=svc&ostemplate=local:vztmpl/debian-12-standard_amd64.tar.zst&memory=2048&cores=2&rootfs=local-lvm:8&net0=name=eth0,bridge=vmbr0,ip=dhcp&unprivileged=1'
scripts/pve-api.sh POST /nodes/{node}/lxc/{vmid}/clone --data 'newid=211&hostname=svc2'

Verify template names (GET /nodes/{node}/storage/{store}/content) and field shapes against the API viewer for the running version.

Mount points — where API ends and host edits begin

Simple mount points can be set via config: mp0=local-lvm:8,mp=/data (a new volume) or a bind mount mp0=/host/path,mp=/data. The API can set these (POST .../config).
But on an unprivileged container, a host bind mount usually has the wrong ownership inside the container unless you set up lxc.idmap UID/GID remapping — that lives in /etc/pve/lxc/{vmid}.conf and is a host-file edit. Likewise features like nesting=1, keyctl=1, fuse=1 (needed for Docker-in-LXC) and any lxc.* raw keys or hookscripts. → use proxmox-host-config and confirm the SSH drop.

Network / VLAN

Before you act

Check version, verify fields, snapshot before risky changes, summarize + get approval. For anything touching lxc.idmap, features, raw lxc.*, or hookscripts, route to proxmox-host-config.