• 0 Posts
  • 256 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle

  • I installed endeavouros on my windows laptop.
    The installer guided me through the partitioning, setting up systemd-boot, and it was all great.
    I had to disable bitlocker in windows (not that bothered about) and secure boot in bios (also not that bothered about).

    Ran smoothly dual booting both for about 4 months.
    Then a windows update hit, and fucked the boot.

    Thankfully, this is a common enough thing that there are plenty of tutorials out there.
    A liveUSB of endeavouros, some tinkering, and I was back up and running.

    The cause seems to be FastBoot, where windows keeps the boot partition mounted. What I think happens is that bios tries to read the boot partition, which is configured/loaded for windows (because it never cleaned up after itself due to FastBoot being on) and boots into windows.
    Since turning off FastBoot, I haven’t had any issues in the past 8 months.







  • Maybe Ukraine couldn’t retake the areas occupied by Russia, but they could deliver a Pyrrhic blow to Kremlin.

    They have delivered a pyrrhic victory.
    Russia thought they could take Kyiv (Ukraine?) on 3 days.
    The fact that Ukraine has resisted so hard, have redefined the modern battlefield, have conducted huge deep strikes…
    Ukraine is winning.

    The reason Ukraine may not be “winning” is because the Russian war machine is huge. Like really really big.
    The reason that Ukraine is “winning” is because the Russian war machine is outdated and corrupt.

    The western opinion of Russia has been devastated. Russia tested themselves, and failed.
    Russia is holding on by their nukes.






  • especially once a service does fail or needs any amount of customization.

    A failed service gets killed and restarted. It should then work correctly.
    If it fails to recover after being killed, then it’s not a service that’s fully ready for containerisation.
    So, either build your recovery process to account for this… or fix it so it can recover.
    It’s often why databases are run separately from the service. Databases can recover from this, and the services are stateless - doesn’t matter how many you run or restart.

    As for customisation, if it isn’t exposed via env vars then it can’t be altered.
    If you need something beyond the env vars, then you use that container as a starting point and make your customisation a part of your container build processes via a dockerfile (or equivalent)

    It’s a bit like saying “chisels are great. But as soon as you need to cut a fillet steak, you need to sharpen a side of the chisel instead of the tip of the chisel”.
    It’s using a chisel incorrectly.


  • I would always run proxmox to set up docker VMs.

    I found Talos Linux, which is a dedicated distro for kubernetes. Which aligned with my desire to learn k8s.
    It was great. I ran it as bare-metal on a 3 node cluster. I learned a lot, I got my project complete, everything went fine.
    I will use Talos Linux again.
    However next time, I’m running proxmox with 2 VMs per node - 3 talos control VMs and 3 talos worker VMs.
    I imagine running 6 servers with Talos is the way to go. Running them hyperconverged was a massive pain. Separating control plane and data/worker plane (or whatever it is) makes sense - it’s the way k8s is designed.
    It wasn’t the hardware that had issues, but various workloads. And being able to restart or wipe a control node or a worker node would’ve made things so much easier.

    Also, why wouldn’t I run proxmox?
    Overhead is minimal, get nice overview, get a nice UI, and I get snapshots and backups