Hello selfhosted community, something weird just happened to my setup while running a routine update.

I’m running docker containers on a couple Debian LXCs through Proxmox, and a regular apt-get upgrade just wiped all my configurations. Somehow it seems to have gutted my databases and deleted the compose.yml files without a trace remaining. Thankfully all my data seems to be intact as far as I can tell.

Did I royally mess something up in all of my configurations or in doing the update? This has never happened to me before. Thankfully I have a backup for the configs that’s about 6 days old, but it’s still extremely annoying. Any hints? Thanks

  • mikyopii@programming.devEnglish
    8·
    9 months ago

    I’m not sure. All I know is that Proxmox doesn’t recommend using Docker in LXCs. It seems Proxmox has much more control over the internals of the container and can break stuff.

    https://pve.proxmox.com/wiki/Linux_Container

    If you want to run application containers, for example, Docker images, it is recommended that you run them inside a Proxmox QEMU VM. This will give you all the advantages of application containerization, while also providing the benefits that VMs offer, such as strong isolation from the host and the ability to live-migrate, which otherwise isn’t possible with containers.

    • Player2@lemm.eeOPEnglish
      43·
      9 months ago

      It was just a matter of time then until something broke? Guess I’ll need to do some more research on how to best manage the services I want to run. Good thing I didn’t come into this hobby hoping to reduce the amount of headaches

      • towerful@programming.devEnglish
        2·
        9 months ago

        I run a debian VM for hosting docker things.
        Its like 500mb extra disk space, and a small ram/cpu hit. But its been solid for me