[SOLVED] Unable to create lxc container

liuhonglu

New Member
Aug 5, 2023
21
1
3
I posted a thread before to ask for help, but there was only one reply: saying that I didn't have enough storage space, which caused the error. However, I had enough free space, and attached a screenshot of the free space, but there was no response, so I had to post again for help.

I got the following error when creating an openwrt lxc container: pct create 102 local:vztmpl/openwrt.tar.gz --rootfs local-lvm:5 --ostype unmanaged --hostname op --arch amd64 --cores 2 --memory 1024 --swap 0 -net0 bridge=vmbr0,name=eth0
WARNING: You have not turned on protection against thin pools running out of space.
WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
Logical volume "vm-102-disk-0" created.
WARNING: Sum of all thin volume sizes (375.51 GiB) exceeds the size of thin pool pve/data and the size of whole volume group (237.47 GiB).
Creating filesystem with 1310720 4k blocks and 327680 inodes
Filesystem UUID: 2b077a96-e504-44bc-bb21-d5aad1280714
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
extracting archive '/var/lib/vz/template/cache/openwrt.tar.gz'
Total bytes read: 1276887040 (1.2GiB, 133MiB/s)

I used this command to create openwrt's lxc container several times a year ago, and there was no such error. Until this time I created it again, this error always occurred
1720433704497.jpeg
 
I used this command to create openwrt's lxc container several times a year ago, and there was no such error. Until this time I created it again, this error always occurred
The "error" is pretty self explanatory. In plain English:
The summed up size of all volumes is bigger than your thin pool.
However you must realize that for each "volume" here, the size is really theoretical - since its a thin-volume. So as long as you don't actually use all of that space - you won't encounter a problem. I imagine this particular LXC got created successfully.

The reason why "several times a year ago there was no such error" is because at the time the total volume size did not exceed the thin pool.
 
Last edited:
Edit: To actually see the amount/s used try pvesm status

I looked at the attached image & see that in fact the container has not been created correctly. So obviously 1GB is not big enough.
 
Last edited:
Yes, I allocated too little space for the lxc container, which led to the error. Thank you for your help.
 
If everything is sorted, maybe tag prefix the thread-title with [SOLVED], (upper right hand corner under title).
 

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!