after 5.4 -> 6.0 docker doesn´t start in a LXC unprivileged + no Backups

tony blue

Well-Known Member
Dec 26, 2017

I upgraded my proxmox Server from 5.4 to 6.0. After the upgrade docker doesn´t start in a unprivileged LXC Containter:

[ OK ] Started Create Static Device Nodes in /dev.
systemd-udevd.service: Failed to reset devices.list: Operation not permitted
Starting udev Kernel Device Manager...
sys-kernel-config.mount: Mount process exited, code=exited status=32
sys-kernel-config.mount: Failed with result 'exit-code'.
[FAILED] Failed to mount Kernel Configuration File System.
[FAILED] Failed to start Docker Application Container Engine.
See 'systemctl status docker.service' for details.

A "systemctl status docker.service" gives this message:

Assertion 'p > 0' failed at ../src/journal/journal-file.c:2482, function test_ob

Before the upgrade from Proxmox 5.4 to 6.0 Docker runs in the LXC Container.

Since the upgrade there is a second failure. I can´t make backups of unprivileged LXC Containers to a NFS share.

What can I do to find the failure of the unprivileged LXC Containers?

Thank you!


I have the same issue with docker + lxc + proxmox 6.
Backups are still working, just did a restore from NFS backup.


*** did a second restore and now the LXC container + docker not updated it is working fine.
Last edited:


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!