No containers starting correctly after certain threshold

Kieran

New Member
Aug 31, 2018
4
0
1
32
Hello,
When I have 22 ubuntu 18 containers running I can't start up any additional containers. They show as started, but the Summary shows minimal activity and services running on them are not active.
[Image 1]
The console lets me type, but nothing else happens. Neither when I press enter, ctrl + c or anything else.
[Image 2]

Note that container 131 was previously working 100% fine and I shut it down to use it as a demonstration when I have 22 other containers running.

Is this a limit of not having a subscription? I'm really confused.

Host doesn't have much load on it
[Image 3]


Second question: I have a container that I cannot stop anymore. I started it after reaching the threshold and made a backup with "stop mode". I tried to cancel the backup to stop and delete the container but it doesn't let me and says "CT is locked (backup)". How do I forcefully kill a container?

Image collection, because I can't post images as a new user: h ttps://pastebin.com/dPQT3Zp8
 
fs.inotify.max_user_instances seems to have fixed the first main problem. Is that change permanent or is it changed back after a reboot?

Still can't unlock the CT though

EDIT: Nvm for some reason I used "qm unlock". "pct unlock" works.
 
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!