• 3 Posts
  • 81 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle



  • Corvids all do this. And they tell the others.

    We had a problem for a few years with ravens punching holes in the tops of grain bags and letting rain and snow in. My cousin shot one from across the yard and threw the pieces on top of the bag. There was a raven funeral for about a day, and we haven’t had a raven pick a hole in a grain in the decade since.

    I’ve seen the same thing happen with magpies when a cat gets one. The other magpies will gather to scream at the cat for a couple of days, but they’ll pack up and move after that.


  • ikidd@lemmy.worldtoMicroblog Memes@lemmy.worldPlease like our AI bro
    link
    fedilink
    English
    arrow-up
    49
    arrow-down
    1
    ·
    edit-2
    6 days ago

    So I went to a poetry performance tonight, and the poet (I’ve watched him for 20 years) says he has a SF poem for the first time.

    The poem was about the year 2525, where the residents of the burned out husk of a planet that we left behind are decanting one billionaire a year. Billionaires started to cryogenically freeze themselves before the collapse of civilization, so there are plenty of frozen bros in dewar flasks powered by solar panels to dig up.

    So they wake up a billionaire a year, and he wakes up tied to a post. He’s asked why he didn’t give a fuck about what happened to the world in the future, and of course his answers were shit. So they set him on fire, as one does with scapegoats. Guess they’ll do it all again next year.

    He called the poem “Burning Man”.

    I applauded, dropped a 20 in his hat, and drove home. Yes, I know.








  • So if I want a new container stack, I make a new Proxmox “disk” in the ZFS filesystem under the Hardware tab of the VM. This adds a “disk” to the VM when I reboot the VM (there are ways of refreshing the block devices online, but this is easier). I find the new block device and mount it in the VM at a subfolder of /stacks, which will be the new container stack location. I also add this mount point to fstab.

    So now I have a mounted volume at /stacks/container-name. I put a docker-compose.yml in there and all data that the stack will use will be subfolders of that folder with bind mounts in the compose file. When I back up, that ZFS dataset that contains everything in that compose stack is snapshotted and backed up as a point-in-time. If that stack has a postgres database, it and all the data it references is internally consistent because it was snapshotted before backup. If I restore the entire folder from backup, it just thinks it had a power outage, replays it’s journals in the database, and all’s well.

    So when you have a backup in PBS, from your Proxmox node you can access the backups via the filesystem browser on the left.

    When you go to that backup, you can choose to do a File Restore instead of restoring the entire VM. Here I am walking the storage for my nextcloud data within the backups, and I can walk this storage for all discrete backups.

    If I want to just restore a container, I will download that “partition” and transfer it to the docker VM. Down the container stack in question, blow out everything in that folder and then restore the contents of the download to the container folder. Start up the docker stack for that folder and it’s back to where it was. Alternatively, I could just restore individual files if I wanted.