Recent content by eth

Here is the full command list which worked in my case: sudo apt update apt install -y pve-headers-$(uname -r) apt install build-essential pkg-config xorg xorg-dev libglvnd0 libglvnd-dev apt install -y dkms pve-headers wget apt install pve-headers-6.5.13-5-pve cp...

You can also downlod the latest file directly from https://images.linuxcontainers.org/images/oracle/9/amd64/default/

Use VirtIO-GPU (or even better, VirGL) and set display memory to 512.

still exists in 8.1.3

Hi! I've created my LXC in a folder (/var/lib/lxc/218), so I could use the full capacity of the host's disk: pct create 218 /var/lib/vz/template/cache/oracle-linux-8-20220719.tar.xz --rootfs=/var/lib/lxc/218 --hostname w18 --net0 name=eth0,ip=10.0.0.18/24,gw=10.0.0.1,bridge=vmbr1 --memory 7196...

Docker is somehow conflicting with proxmox routing. Upon scanning the blogs/forums, there is no solution where proxmox and docker can live together on the same level. I ended up creating a CT (not LXC) with Centos 8 and putting docker inside of it. This is a clean solution, since each level...

Anyone found a solution for this? I just installed docker on the host and lost internet connection on the Proxmox LXC containers.

did you manage to get this resolved? I'm hitting exactly the same problem here.

Is there a way how I can move the LXC to another cluster node through the GUI? I don't care about live migration - I can shut it down, I just need the files / configs transferred.

Hello! I use node directories for storing my LXC container data. This allows me to use the full disk space of the node more effectively (instead of carving out a part of it that might not be used fully). Here is the config of one of the LXC's: arch: amd64 features: fuse=1,nesting=1 hostname...

Well, I have what I have. These are not new servers that I'm working with.

I would like to lock 1GBPS on my network cards that sometimes fall back to 100mbps. For now I'm using a custom-made bash script, but it would be amazing if network interface speeds could be assigned through the web interface.

If you're not using Qemu, this can also be related to faulty /etc/init.d/ scripts which are causing the shutdown to abort on a system level. They are very hard to diagnose, since there is nothing in the logs. So, if you have custom /etc/init.d scripts, they are most likely the problem.

Such a pain figuring out what input is the active one:

Hello! I'm using a very old KVM system to access my datacenter and I've noticed that the proxmox installation interface is very sluggish: Perhaps it's possible to remove all gradients (or redo the interfaces in ncurses?). Also, the window barely fits into a 640x480 kvm window. Also, I have a...