Recent content by unam

Hi folks, I also have the problem and I'm very happy to find out that it's already solved :) Would you have any news about your patch integration @ggoller ? Regards,

I tried enable keyctl too. But it still does not work. Here is my config file arch: amd64 cores: 1 features: fuse=1,keyctl=1,nesting=1 hostname: ct-wekan memory: 2048 nameserver: 10.xxx.xxx.xxx ostype: debian rootfs: lv_thin_vms:vm-104-disk-0,size=15G searchdomain: xxx swap: 1024...

Hi, Here when I try snap install wekan I always have an error : error: system does not fully support snapd: cannot mount squashfs image using "fuse.squashfuse": mount: /tmp/sanity-mountpoint-494747820: wrong fs type, bad option, bad superblock on /tmp/sanity-squashfs-152452673...

Hi, You are right when you says "Avoid creating VMs if you're not sure it won't eat up all the remaining space". I take care about this because of my job as a sysadmin. The fact is, finals / casuals proxmox users don't care , and play with it as a sandbox and are not aware of all this...

Quick reply, I tried another way by deleting the meta0 lv created by a repair attempt and start another repair root@hypervisor04:~# lvremove VGRAID0/lv_thin_build_meta0 root@hypervisor04:~# lvconvert --repair -v VGRAID0/lv_thin_build Preparing pool metadata spare volume for Volume group...

Hi, I have a node running latest up to date Proxmox version. I configured lvm thin provisionning for users with a Raid0 composed with 2 SSD for about 1To. Maybe a misconfig or bad usage made it crash. A user provisionned a template with a storage of 500Go. Everything was running fine for our...

Fine, it is working, thanks. Anybody knows why this file is missing ? Why does it don't come with an update ? Regards,

Wow, thank you. I already heard about jq but never used nor check what it was. It's done for now, thank you I can play with the api and with the informations I need. Regards,

Hi, Following my previous post concerning our custom deployments, I am trying to build a dev environment for our team. The use case is : - lxc rootfs creation with packer via Jenkins - push rootfs on proxmox - import rootfs as new lxc - start some jobs into theses new containers I am writing...

The two solutions are finally working like a charm. For the second one, I just had to edit the configuration with pct set 999 --ostype debian Thanks again.

It does not work :/ Would you have any other idea ? Regards,

Hi there, We are using packer to build rootfs to deploy appliances on our proxmox servers for lxc and docker. I tried to create a container based on an imported rootfs with folowing command line pct create 999 /var/lib/vz/template/cache/packer-debian-template.tar.gz --arch amd64 --hostname...

Thanks for your answer, I already checked this page but I did not find a solution. I was reading again in the morning and find a kind of solution : - On my libvirt host : qemu-img convert -O qcow2 /dev/VG00/vm-XYZ ./vm-XYZ.qcow2 scp ./vm-XYZ.qcow2 root@mynewhost - On my new proxmox host qm...

Hi, I just started a lab with 3 hypervisors : - 2x Intel Xeon - 256Gb ram - 4x960Gb SSD Intel - 4x4To WD I just configured a ceph storage with crush replication rules for ssd and hdd. A the moment, I just configured two nodes, the latest is in production, using Debian and libvirt to provide lxc...