Lachlan, creator of lemmyunchained.net

  • 7 Posts
  • 173 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle


  • LachlanUnchained@lemmyunchained.nettoSelfhosted@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    10
    ·
    edit-2
    1 year ago

    AI GENERATED:


    The ttionya/vaultwarden-backup tool is intended to work with Docker volumes. However, you are using a bind mount, not a named volume. Bind mounts refer to the use of local folders to store data, as in your case (./vaultwarden:/data/), while volumes create a specific place within Docker’s own filesystem for the data.

    Although this tool is designed for volumes, it might still work with bind mounts if the backup container can access the data directory. You would need to modify the volume line in the Docker Compose file for the backup tool to point to the directory where your bind mount is located, i.e., to point it to your local ./vaultwarden directory.

    So, you might want to adjust your docker-compose.yml file like this:

    services:
      vaultwarden-backup:
        image: ttionya/vaultwarden-backup:latest
        container_name: vaultwarden-backup
        environment:
          - PUID=1000
          - PGID=1000
          - BACKUP_INTERVAL=12h
          - PRUNE_BACKUPS=7D
        volumes:
          - ./vaultwarden:/vaultwarden:ro
          - ./backups:/backups
        restart: unless-stopped
    

    In this configuration, ./vaultwarden:/vaultwarden:ro line is the key. It mounts your local ./vaultwarden directory to /vaultwarden inside the backup container (readonly mode), which should allow the backup tool to access the data.




  • A few years back, I moved into an old farmhouse in the countryside. It was peaceful, except for the noises that would come from the attic every night, a soft thumping like someone walking around. After a couple of sleepless nights, I finally mustered the courage to check it out.

    I climbed up to the attic with a flashlight. It was full of dusty old furniture and trinkets, probably from previous tenants. As I was examining a pile of old newspapers, my flashlight caught something - a pair of eyes glowing in the dark, staring right back at me. I nearly dropped the flashlight in shock. As I shone the light in the direction, I found an old portrait of a woman. The eyes were eerily lifelike. I convinced myself it was just the way the light was hitting it.

    The noises didn’t stop, but I learned to live with them. But the weirdest part was when I left the house a 6 months later. The movers came to get my stuff, and I told them to leave everything in the attic, I’d Grabe those items myself. I mainly needed movers for the big heavy stuff. Later, when I returned to pick up some remaining items, the portrait was gone.

    To this day, I still can’t figure out where it could have gone, why just that. Probably some completely logical explanation, but it still gives me chills when I think about it.








  • Sometimes, it’s surprising how life unfolds. I remember back in my second year at boarding school, we were all set to return for another term, standing on the train station platform. Fooling around, we missed the train.

    With no other options and perhaps a bit of youthful audacity, we took dads old ford and we ended up driving it all the way to school.

    The car broke down, we almost got caught. Then crazily, we crashed into a famous tree on campus.

    However, as wild as that was, missing that train might just have saved us.

    We later found out that the Chamber of Secrets had been opened around the time we were meant to be on that train. A deadly monster, a Basilisk, was slithering around the castle, able to kill just by meeting your gaze.

    Who’s to say we wouldn’t have bumped into it, had we made that train? With our track record of stumbling into trouble, it seems more than likely. It’s a chilling thought.

    Xoxo Ron