Paste the lxc.idmap lines from your container config, enter the host path, LXC path, and mount point index. The tool detects which UID/GID rows are passthrough mappings, generates the replacement mpX: line for /etc/pve/lxc/<CTID>.conf, and shows the cleanup commands to remove the old lxc.idmap block.
Requires Proxmox 8.1 or newer (kernel 6.x). The backing filesystem must support idmapped mounts: ZFS, ext4, and XFS all work. Older NFS or CIFS exports may not.
No passthrough rows detected — paste your lxc.idmap block above.
<CTID>.conf line
Enter a host path and LXC path to generate the config line.
Fill in the fields above to generate cleanup commands.
What this tool does
Legacy LXC containers on Proxmox used a lxc.idmap block in <CTID>.conf plus matching entries in /etc/subuid and /etc/subgid to remap container UIDs/GIDs to host UIDs/GIDs. A typical setup for passing through a single host user (UID 1000) looks like this:
lxc.idmap: u 0 100000 1000
lxc.idmap: g 0 100000 1000
lxc.idmap: u 1000 1000 1
lxc.idmap: g 1000 1000 1
lxc.idmap: u 1001 101001 64535
lxc.idmap: g 1001 101001 64535
The tool reads those lines, picks out the passthrough rows (containerId === hostId), and builds the idmapped mount line that replaces them — mp0: /mnt/media,mp=/media,idmapped=1. It also shows the sed command to strip the old lxc.idmap lines and a reminder to clean up the matching subuid/subgid entries.
Background on UID/GID mapping, default offset layouts, and when traditional lxc.idmap is still the right approach.