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.worksEnglish
    2·
    2 days 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.worksEnglish
        4·
        2 days 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
          1·
          2 days ago

          I think linux does fstrim oob.

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

          • ohshit604@sh.itjust.worksEnglish
            1·
            19 hours ago

            It’s been about a day since this issue and now I’ve been keeping a close eye on my local-lvm, it fills fast, like, ridiculously fast and I’ve been having to run sudo fstrim / inside the VM just to keep it maintained. I’m finding it weird I’m now just noticing this as this server has been running for months!

            For now I edited my /etc/bash.bashrc so whenever I ssh in it’ll automatically run sudo fstrim /, there is something I’m likely missing but this works as a temporary solution.