Search results

Hello all, Im trying SDN technology preview on PVE 8.4. I ran into a problem like many others before me. BGP-EVPN + VxLAN. It is working if you have all PVE nodes in one local network (one VLAN) only. If you put some nodes in different networks, it breaks. The core of problem is the FRR can't...

I got this error today. Can confirm this is a problem after 2 years later.

Hello all, is it possible to redefine "local_network" by enumeration with several IP addresses? I have 3 fresh installed standalone nodes in 3 different datacenters. Each node has its own public IPv6 address. IPset "management" is set on all nodes, firewall is enables with default action DENY...

Is there any solution for someone, who wants to stay with unpriviledged containers? UIDs in AD are pretty high number as getent passwd user.joe@example.com user.joe@example.com:*:1333222111:1333222111:Joe User:/home/user.joe@example.com:/bin/bash

And what is a status of CVE-2022-0492 (cgroup-v1 escape)? Is it patched in pve-kernel-5.13.19-6-pve ? Thank you

Hi, I like to install ceph on 3 proxmox nodes with 2 network cards each (NIC1, NIC2). After reading wiki and some howtos, i didnt understud one detail. Proxmox nodes uses device NIC1 with network address 192.168.0.0/24 Can I set two cephs networks as "public_network=192.168.0.0/24" on NIC1...

Hello, I like to express my humble opinion. As many other people reported it before, the sentence: "For those you will see a bigger text area, simply copy all the credentials KEY=VALUE pairs in there." leads to "simple copy" and it is wrong. Problem is the quotes and double quotes that must...

Can someone tell me, what Im doing wrong, please? # podman run hello-world Error: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"proc\\\" to rootfs...

I did saw it at linuxcontainers.org, what should be primary source of lxc templates. Can we ask someone from Proxmox staff to kindly refresh their repo, please? Thank you

This bug is fixed on upstream, maybe. Look at template opensuse-20200315. "pveam update" shows old template still.