Recent content by silverstone

  1. S

    apt-cacher-ng and proxmox-offline-mirror-docs / proxmox-offline-mirror-helper

    Thank you for your Reply. I've also had enough due to these 2 stupid Packages and decided to just mirror the entire pve-no-subscription and pbs-no-subscription Repositories. I am using a heavily patched Version of debmirror (Perl ... sigh :rolleyes: ) so that I can also selectively exclude...
  2. S

    VM isolation into its own VLAN

    If the Router doesn't understand VLANs, then Router's traffic will default on the default untagged VLAN (Default ID: 1). You can configure the untagged VID in Proxmox for the NIC, or add another Virtual NIC and set that as untagged instead.
  3. S

    apt-cacher-ng and proxmox-offline-mirror-docs / proxmox-offline-mirror-helper

    Ever since Proxmox VE started requesting / recommending the installation of proxmox-offline-mirror-docs / proxmox-offline-mirror-helper (either as Dependency or as recommended Packages), I had all Clients failing to download these Packages via apt-cacher-ng. It causes a HTTP 400 Bad Request...
  4. S

    Mellanox ConnectX-3 & Proxmox 9.1

    Well, for some weird Reason the -I include Directive didn't seem to work. Editing the File /var/lib/dkms/kernel-mft-dkms/4.22.1/build/mst_backward_compatibility/mst_pci/mst_pci_bc.c manually and prexing the Paths with ../../nnt_driver/ did the Trick for me: #include <linux/module.h> #include...
  5. S

    Proxmox-VE

    Just install Proxmox VE on top of Debian Trixie :) . I've been doing that for several Years now since I also had VGA Issues back in the Days. Script Set is by no means perfect but it works well enough for me. Configure based on Example Config...
  6. S

    [SOLVED] Docker inside LXC (net.ipv4.ip_unprivileged_port_start error)

    For me it's not so much about RAM as it's about Disk Space. RAM wise I agree that with Dynamic Memory Management (VM Memory using Balloon Feature) it works already much better. I use podman (rootless) instead of docker. As a Reference Point, although of course that's highly subjective, I have...
  7. S

    [SOLVED] Debian 13 LXC networking.service failed

    I lost approx. 1h this evening with the Error dhcpcd[139]: eth0: ipv6_start: Cannot assign requested address. Nothing worked. I tried Managed Host Configuration (checked), Unmanaged Host configuration (unchecked), DHCPv6, SLAAC, Static. Nothing worked. In desperation and seeing this Post...
  8. S

    Trying to set IPv6 token, adding LXC options in container config file

    Late Reply but one Option might be to mark the File as something that Proxmox VE shouldn't touch. I do this for /etc/resolv.conf inside a PiHole LXC Container, but I guess with the right Name it would work for anything. File /etc/.pve-ignore.resolv.conf: #...
  9. S

    Nothing works anymore "can't lock file '/run/lock/lxc/pve-config-xxx.lock"

    I just had this happen to me. It wasn't very straightforward, but this seems to work: Kill the lxc-start Process that started the Container Manually remove the Lock file Use lxc-stop with --kill and --nolock Arguments to (try) to stop the Container (most likely it already stopped) Use pct...
  10. S

    LXC Unprivileged Container Isolation

    Actually my Script (which I improved quite a bit in the Version I have locally) works OK. Now the only Issue is about the NFS read-only Share Mount that was bind-mounted inside the Container (Group lxc_shares or 100000) which now is not accessible anymore :(. I might need to setup an...
  11. S

    LXC Unprivileged Container Isolation

    Thanks for your in-depth Explanation :) . Maybe to add yet another Attack Surface related to Mountpoints: what about the Case of a shared GPU via one or more of the following dev0: /dev/dri/card0,mode=0660 dev1: /dev/dri/renderD128,gid=992,mode=0666 lxc.mount.entry: /dev/net dev/net none...
  12. S

    Mountpoints for LXC containers broken after update

    Maybe for me it works fine because it's supposed to be read-only anyways. It's basically all my Scripts I have on my NAS, mounted as read-only for Security Reasons: mp0: /tools_nfs,mp=/tools_nfs,mountoptions=discard;noatime,ro=1 These show up as owned by nobody:nobody in the LXC Container (it's...
  13. S

    LXC - Remount mountpoint without rebooting Container

    A reboot of the LXC Container does NOT work for me. I need to first stop the LXC Container. Wait a few seconds. Then start the LXC Container again. In a normal Situation, the Share is already mounted on the Host. The only "Fix" I could find for the initial (after Host Boot) is: pvenode config...