![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Last time I canceled it it was very easy to do (amazon.ca)
Last time I canceled it it was very easy to do (amazon.ca)
In my personal experience it has been getting consistently worse over the last 6 or so years. It used to be nearly perfect but now it is somewhat common that the directions will be wrong or misleading
It looks like NAND and therefore SSD pricing is trending up currently due to some supply limitations. If you want to get some large drives it might be best to try to do it soon, or be prepared for a wait/inflated pricing.
Syncthing works very well for Logseq, I use it on 4 different devices and changes only take a couple seconds to be synchronized. The app even automatically refreshes the data when a change is made so you don’t have to worry about only having one instance open at a time.
Using the F40 preview with KDE and a regular update from Discover rolled xz back to the known good version 5.4.6
Interesting, I had zero problems with the RPMFusion Nvidia driver on Fedora on two machines that did have TPM and secure boot. In fact, it was surprisingly easy.
It’s also running on Chromium
The question was “why,” you may as well be protesting the addition of a new codec
Whenever I break something and can’t figure it out, I just make sure anything important is backed up and do a clean reinstall. Someone else might have a better answer though
I just enjoy putting on a hoodie, turning down the lights, and running updates manually every couple days. Makes me feel like hackerman
That’s what I do, everything local only and then remote access through Tailscale
This is what I do for Logseq, works very well
Rockstar was doing a similar thing I believe
Most docker releases I have seen include a template yml
Update in case anyone is interested: I figured out what caused the problem. When I mounted the new drive I used to store my configurations onto Proxmox, I completely forgot to make the relevant /etc/fstab entry. The drive mounted successfully so I didn’t realize at the time that I had forgotten to do that step. The update I ran from apt-get included a kernel update, so I restarted the machine to complete it. Since I hadn’t modified fstab, my new drive was not mounted when the system started up again. Even though the drive wasn’t mounted correctly, I still somehow had access to some incomplete version of the files in its directory (no idea how that works). So no fault of Docker, LXCs or Proxmox, purely PEBKAC.
Despite getting the files back I will still work towards a more resilient system and more regular backups.
The files were on a mountpoint, completely separate drive. This has also been the case for all the previous times I ran an update, though I did recently move these files to a different drive mounted the same way. I got some sort of permission wrong maybe?
Will definitely set up a better backup system as soon as I can
Interesting, I think I did actually do that. I guess my best bet for now is to just nuke the LXCs then and move everything to a new VM. Thanks for the advice!
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
Clearly the correct action is to own one and simply not use it
Streets ahead