Setting up lxc.idmap break webgui monitoring

Sep 28, 2019
24
4
23
42
I setup a few LXC containers with idmaps to and now I don't get any running/stopped/summary data in the webgui. The changes I made were:

* Add shared users to /etc/passwd:
Code:
nas-backups:x:5002:5002::/home/nas-backups:/usr/sbin/nologin
nas-plex:x:5005:5005::/home/nas-plex:/usr/sbin/nologin
nas-apt-cache:x:5003:5003::/home/nas-apt-cache:/usr/sbin/nologin

* Add lxc.idmap entries to map ids [5000-5099] to 107.conf
Code:
# uid map: from uid 0 map 5000 uids (in the ct) to the range starting 100000 (on the host), so 0..4999 (ct) → 100000..104999 (host)
lxc.idmap: u 0 100000 5000
lxc.idmap: g 0 100000 5000
# we map 100 uid starting from uid 5000 onto 5000, so 5000 → 5000
lxc.idmap: u 5000 5000 100
lxc.idmap: g 5000 5000 100
# we map the rest of 65535 from 5100 upto 105100, so 5100..65535 → 105100..165535
lxc.idmap: u 5100 105100 60435
lxc.idmap: g 5100 105100 60435

* Allow range to be mapped via subuid/subgid files, each added:
Code:
root:5000:100


After those changes the container boots fine, I can ssh into it and the idmap is in effect. The UI shows "Status: unknown" in the container list and the Summary page just sits with a spinner. I did see the following error in the UI the first boot of the container after adding the idmap:

Code:
can't open '/sys/fs/cgroup/blkio/lxc/107/ns/blkio.throttle.io_service_bytes' - No such file or directory (500)
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!