That is a sign of containers created and and maybe also deleted. I don’t remember which log appears when.
What I saw often is that when I boot the OS, network related settings, issuescan slow down the booting process, but after about 2 minutes, it usually continues. It is worse when more than one delay happens, but I don’t see why running Docker would block the entire booting process. I understand thaty ou waited 2-3 hours so that is wy more than normal
We had multiple Proxmox related issues. I don’t remember endless booting loop, but I know proxmox related issues are not rare. I would recommend this the following topic, especially the last post:
The original issue is different but you could still check if apparmor is enabled and what happens if you disable it. (even if it worked for you before)
You mean the VM was created with those scripts? That shouldn’t matter.
Can you also share the output of docker info and docker version? Remove any private info from the output before sharing like IP, domain, username and so on. When you share the outputs, please, use code blocks like this:
```
output here
```
So 3 backticks before and after the code if you are using the markdown based message composer.
But based on the logs, it is suspicious that the eth0 interface was renamed after the container-related logs. Could be totally normal. I am not sure. If Docker, containerd or runc were automatically updatd, that could also cause problems.