Search results

That did work. I have sized down a container from 40 to 8 GB. It would be neat if during restore the size of the container could be configured.

Since pct rescan crashes I've deleted the snapshots with lvremove. I still don't have an idea why the problem surfaced in the first place. Deleting a snapshot should not cause a lockdown.

Thanks. Since the UI doesn't allow to size down containers I plan to do a backup, change the rootfs size inside pct.conf, then restore with smaller size.

I mean the filename of the VM config file inside the tar archive where the ram and storage size is stored. I know dump files are in /var/lib/vz/dump

What is the filename?

When restoring a .tar.gz backup of a container the correct storage and ram size is restored too. Where is that information saved? Inside the .tar.gz backup?

pct rescan rescan volumes... Use of uninitialized value in hash element at /usr/share/perl5/PVE/LXC.pm line 2002.

I've tried to delete a snapshot of a container in Proxmox 6.1-8 web ui. It was the first one of 13 snapshots. Got a message that the snapshot doesn't exist. The container was now locked. I've unlocked it in the shell. pct unlock 103 After that tried to delete the snapshot again, with the same...

Das wars. Danke, jetzt gehts!

Zum testen habe auf dem Host den Ordner /temp erzeugt und wollte ich nun auf dem Gast mounten. pct stop 104 pct set 104 -mp0 /mnt/bindmounts/temp,mp=/temp pct start 104 Ergebnis: Job for pve-container@104.service failed because the control process exited with error code. See "systemctl status...

Ich hab unter Proxmox 5.2-10 einen Container mit Debian 9.5. Das Volume des Containers liegt auf dem local-lvm. Ich würde gerne in dem Debian Guest auf /tmp des Hosts zugreifen. Wie stelle ich den Mount an?