Docker docs:

Docker routes container traffic in the nat table, which means that packets are diverted before it reaches the INPUT and OUTPUT chains that ufw uses. Packets are routed before the firewall rules can be applied, effectively ignoring your firewall configuration.

  • ohshit604@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    21 hours ago

    Okay so I’ve done some digging and got my VM to boot up! This is not Podman’s fault, I got lazy setting up Proxmox and never really learned LVM volume storage, while internally on the VM it shows 90Gb used of 325Gb Proxmox is claiming 377Gb is used on the LVM-Thin partition.

    I’m backing up my files as we speak, thinking of purging it all and starting over.

    Edit: before I do the sacrificial purge This seems promising.

      • ohshit604@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        ·
        20 hours ago

        So I happened to follow the advice from that Proxmox post, enabled the “Discard” option for the disk and ran sudo fstrim / within the VM, now the Proxmox LVM-Thin partition is sitting at a comfortable 135Gb out of 377Gb.

        Think I’m going to use this fstrim command on my main desktop to free up space.

        • sip@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          13 hours ago

          I think linux does fstrim oob.

          edit: I meant to say linux distros are set up to do that automatically.