My LXC stopping more frequently

P

promoxer

Member
Apr 21, 2023
222
23
23
My LXCs started stopping randomly after over 1 year of use and I cannot find any logs on why it crashed. These LXCs are occasionally re-created by scripts, so they are quite consistent.

How can I find the reason for them stopping? Or can I get them to self restart?
 
Last edited:
promoxer said:
I cannot find any logs
Click to expand...
So what is this?

Are you running docker in your LXCs? You should use a VM for that.

Quote from wiki:
If you want to run application containers, for example, Docker images, it is recommended that you run them inside a Proxmox QEMU VM. This will give you all the advantages of application containerization, while also providing the benefits that VMs offer, such as strong isolation from the host and the ability to live-migrate, which otherwise isn’t possible with containers.
Click to expand...
 
Those are additional failure logs that I found in my logs as I was trying to figure out what happened to the LXC.

What is the context of the quote? i.e. what's the quoted difference about running docker in LXC and VM?
 
Last edited:
  • Like
Reactions: gfngfn256
You can search these forums & the general web on running docker in an LXC, but basically it comes down to 3 things when trying containerization inside containerization:

  • Updates/changes within the host system & storage can break that "flimsy" containerization inside containerization.
  • Security issues in a containerization inside containerization environment, where you usually give various accesses to host resources (usually inevitable).
  • Running a VM for docker is the streamlined & clean approach - & a lot less work.

I know that resources is usually the mindset when approaching the docker VM/LXC install issue - but even in a VM this can be done pretty efficiently. Have you ever tried an alpine VM to run docker? You'll be surprised how small/resource efficient it can be!
 
promoxer said:
That does not justify why logs are entirely missing in PVE
Click to expand...
I agree - but I'm still pretty sure that that overlayfs: failed to clone lowerpath error is linked to the LXC's.
As you probably well know - any system "crash" can effect many areas - and sometimes those critical logs can themselves "fall victim" to the crash. I completely understand your frustration of not getting the info you seek from logs - we all go through it at some point!

I remember reading once of the problem being linked to overlayfs on top of ZFS within a nested LXC- but all I can find now is this.

I must point out - I don't use or have experience with your use case. Good luck.
 
You must log in or register to reply here.
Top Bottom