all 15 comments

sorted by: hot top controversial new old
[–] 40 points 9 months ago (4 children)

Who tf actually uses Docker Swarm anyway?

  • source
  • hideshow 4 child comments
  • [–] [S] 1 point 8 months ago

    I do!

    Kubernetes is a nightmare and overkill for most things we need to run, and Docker Swarm is super easy to setup and maintain.

    We only use it for one application, though. The app needs to scale horizontally and scale up and down with demand, so I put together a 6 node swarm cluster just for it. Works great, though the auto scaling required some helper scripting.

  • source
  • parent
  • [–] 20 points 9 months ago (1 child)

    Not indexing from 0? Now I see why you're not using quadlets or k3s or k8s

  • source
  • hideshow 1 child comment
  • [–] 11 points 9 months ago

    When I try to explain what I'm working on at work to my wife...

  • source
  • [–] 5 points 9 months ago
    [–] 2 points 9 months ago (5 children)

    what's more, I can't load this meme normally, my pihole says "no reply received" for the single domain of dubvee.org

  • source
  • hideshow 5 child comments
  • [–] [S] 3 points 9 months ago* (4 children)

    Your IP may unfortunately be inside a CIDR block that largely does nothing but spam my infrastructure with script kiddie tomfoolery. Firewall rules apply to my authoritative DNS servers as well.

    Edit: If you would like me to whitelist it, DM me your IP and I'll add a narrow exception.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 9 months ago (3 children)

    but I don't run a recursive resolver, I use quad9 as upstream. Shouldn't they return a response even if I was blocked?

    dig confirms with EDNS extensions that the response is coming from quad9. the error says "no reachable authority" so it must be at least partly what you say, but I think you ended up blocking a DNS provider.

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 3 points 9 months ago* (last edited 9 months ago)

    Ugh. Thanks. It's quite possible, though maybe just a regional one? I did inadvertently block one of the IPs Let's Encrypt uses for secondary validation, so this may be another case of that.

    I get a shitload of bad traffic from the southeast Asia area (mostly Philippines/Singapore AWS) and have taken to blanket blocking their whole routes rather than constantly playing whack-a-mole. Fail2ban only goes so far for case-by-case.

    Here's the image from the meme from an alternate source:

  • source
  • parent