• 0 posts
  • 7 comments
Joined 3 years ago
Cake day: June 15th, 2023
  • Truth is, it is availible in the normal kernel now and several distros offer it from start.

    You may want to rephrase this. ZFS license (CDDL) is still incompatible with the Linux kernel (GPL) so it’s not part of the kernel sources and needs to be compiled as an out-of-tree module against the kernel you’re running.

    Some distros make such modules available by default with some of their official kernels, some don’t. You can get it installed on most distros but the manner of doing so and the amount of support you can expect from the distro varies wildly. If install/update is a manual operation you run the risk of the module falling out of sync with the running kernel.

  • TLDR: Quadlets are systemd units adapted to orchestrate containers.

    Once upon a time Podman wanted to be a FOSS reimplementation of Docker, complete with compose, but it didn’t want to have the same approach with a rootful daemon so it focused on running containers “manually” via podman command.

    But you need orchestration in order to autostart containers, restart them when they die etc. so it landed on systemd which already does orchestration among other things.

    Quadlets aren’t quite the same as compose because they were designed for a very different system and with different goals in mind. Also the rootless approach doesn’t necessarily work with every docker image. If you’re considering a migration it’s going to be a bit of a chore and you’ll have to labor extensively to get some apps to work.

    The old compose compatibility layer of podman is still around but it’s not 100% compatible anymore and you have to account for the rootless approach and still do some orchestration.

    It’s not necessarily “better” or “worse” than docker, just different, so prepare to learn a different way of doing things.

  • Normally I’d say that would be completely idiotic. There’s so much competition in this space, if Docker tried anything like that it would get replaced instantly.

    But I’m not sure it would surprise me.

  • Having access to port 80 on the IP associated with a domain but not to the DNS raises some interesting questions. 🙂

    Unless it’s purely a matter of personal preference but I for one don’t see why you’d want to do HTTP-01 (as a self-hoster) unless forced. It can’t do wildcards, for one thing. And you need an A record pointing to your public IP, and if your public IP is dynamic you need to do DDNS, and open port 80 and so on. That’s a lot of moving pieces that make automation hard.

    Also, if you’re doing DDNS there’s a chance the DNS has some sort of API that might also work for certbot. Granted it’s not a given, I’ve seen registrars that offer a DDNS link but not something you’d call an actual DNS API.

    But anyway finding a decent DNS provider with a certbot-friendly API is not that hard.

  • Can I recommend that you move that record to the local DNS? Assuming your router’s firmware has this feature and you can access it.

    Private IPs in public DNS are associated with certain types of attacks and they get filtered by some DNS servers, routers or ISPs so you may run into intermittent “unexplained” hiccups.

    Secondly, if your internet ever goes down in the middle of the night and the records expire from the local DNS cache by morning, you won’t be able to resolve anything on your LAN anymore. Which is a pity because it’s unnecessary, your local setup can work fine independent of the internet connection.

    Last but not least, there are actors out there that use a variety of methods to gather information about the infrastructure behind each domain and the least such information you put out there, the better.

    Run your domain through DNS Robot to get an idea.