What is the current recommended way to have xfs instead of ext4 as filesystem for a lxc container mount point (mp0)?
I am trying to create a xfs file system for a container mount point. But it always ends in a container crash on startup:
root@tokoeka /mnt # pct start 110 --debug...
I assume this has to do with the UID mapping for the unprivileged container, as described in https://pve.proxmox.com/wiki/Unprivileged_LXC_containers. My problem is that I need the converted mass data with www-data:www-data permissions. How can I fix these permissions?
I managed to mount the converted storage. But inside the container, the new mount point is mounted with wrong permissions (nobody:nogroup instead of root:root). And there is no way to change these permissions, chown -R doesnt work:
drwxr-xr-x 4 root root 4096 Feb 24 13:35 .
drwxr-xr-x 22...
I played a bit and the correct syntax seems to be
pct set 116 -mp1 volume=data:116/vm-116-disk-2.raw,mp=/mnt/data2,backup=1
But still I get errors when I try to start the container with the new mountpoint:
run_buffer: 321 Script exited with status 255
lxc_init: 846 Failed to run...
I dont understand the correct syntax for pct set to mount la local loop device from a raw file.
I have a *.raw file which was converted from a kvm VM (qcow2 converted to raw). It contains mass data and shall be attached into a lxc container. As far as I understand...
I am migrating some KVM VMs to lxc. The direct conversion of the qcow2 images fails on the command line:
qemu-img convert -f qcow -O raw vm-109-disk-1.qcow2 /mnt/data/images/114/vm-114-disk-3.raw
qemu-img: Could not open 'vm-109-disk-1.qcow2': qcow (v1) does not support qcow version 3
Try the...
ok, that was the problem obviously.
The login data (username and PW) for the web access come from a connected keepass database. There we had [username@pam] for all logins. This worked without problems up to PVE 7.0. Looks like the behaviour of PVE 7.1 is different at this point. You need to...
The PVE at https://tokoeka.netzwissen.de is a single node, so, I have no /etc/pve/domains.cfg
journalctl -fu pveproxy.service shows nothing interesting, but
root@tokoeka /etc/pve # journalctl -fu pvedaemon.service
-- Journal begins at Sat 2021-06-12 04:23:15 CEST. --
Nov 25 23:36:07...
I just looked at the web UI of our system again. I still cant login into the Web UI after the upgrade from 7.0 to 7.1. Only the ssh logins are still operational.
The logs show nothing (/var/log/pveproxy/access.log). I have no idea how to fix this and all web UI users are affected. I tested with...
Confirmed, one day after the update 7.0 >> 7.1 all web logins with @pam users fail. No matter if they use U2F or not.
The shell login (ssh) is still working though. /var/log/pveproxy/access.log has no useful info for debugging.
Any ideas how to debug this?
My last mac spoofing complaint from hetzner was closed at 13.11. But it may come up again, I dont know ...
Maybe they changed their detection script a bit, but its hard to tell without any written reply with technical details.
On PVE 7 I get the following error for the letsencrypt cert renewal (task acmerenewal):
root@tokoeka ~ # pvenode acme cert renew
Loading ACME account details
Placing ACME order
Order URL: https://acme-v02.api.letsencrypt.org/acme/order/63630251/35385412630
Getting authorization details from...
@proxmox Staff: a growing number of users is runing into problems with their hosters. We need a final solution, otherwise proxmox can not be called a "save solution" to use in a professional hosting environment!
Hi Oguz, thanks for the hint, and I think i found the problem. For one of the lxc machines, the separate data partition is accidently located on the pve-root "local" storage instead of the separate mount-point for "data" on /mnt/data which is much bigger ;-(. Anyway, in the middle run, time for...
A few days after upgrade from PVE 6.4 to 7.0-11 I see a strange message in the shell:
root@tokoeka ~ # du -hs / | sort -rh | head -5
du: cannot access '/var/lib/lxcfs/cgroup': Input/output error
du: cannot access '/proc/77889': No such file or directory
du: cannot access...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.