Updating Proxmox breaks docker LXC

[LordRatner]

Hello,

I had an LXC running Docker, running Compreface. It was working fine until I upgraded Proxmox and restarted the servers. A couple things I don't understand happened.

1. My Docker LXCs did not automatically start the containers when the LXC booted up. And Many of them had to do fresh pulls when I ran `docker compose up -d`
2. In the specific case of this LXC, the pull fails with the following error:
   `failed to register layer: ApplyLayer exit status 1 stdout: stderr: unlinkat /usr/local/lib/python3.7/site-packages/numpy-1.19.5.dist-info: invalid argument`

I tried restoring a backup from before the Proxmox update. It required the fresh pull and gave the same error.

I tried a fresh docker LXC and fresh install, it works fine. But I'd rather avoid a fresh start on this service.

What could the update have broken?

Thanks!
Seth

 

[LnxBil]

If you want consistent operation, don't use LX(C) containers for docker as many people have already pointed out in various posts. A multitude of things can break if you run Docker inside of LX(C), even if you find a working configuration. The next update can and will break it. It was not meant to run together and it is a constant battle.

 

[Neobin]

If you want to run application containers, for example, Docker images, it is recommended that you run them inside a Proxmox QEMU VM.

https://pve.proxmox.com/wiki/Linux_Container

In my humble opinion, this should be rephrased from only a recommendation to use Docker inside a VM to a strong discouragement to use Docker inside a LXC (and even more on the host itself); especially since one can find exactly those statements from the Proxmox developers on this forum:

• https://forum.proxmox.com/threads/t...-really-messed-up-my-boxes.119933/post-520845
• https://forum.proxmox.com/threads/d...r-log-apt-invalid-argument.119954/post-521620
• https://forum.proxmox.com/threads/n...r-lxc-container-nicht-mehr.119895/post-520940
• https://forum.proxmox.com/threads/n...r-lxc-container-nicht-mehr.119895/post-520945
• ...

Edit: I created a ticket to suggest rephrasing it in the documentation:
https://bugzilla.proxmox.com/show_bug.cgi?id=4712