4 ms·

I run servers for one of the biggest open source multiplayer games on github. (tgstation/tgstation) Everybody asks why we don't do cloud, and time and time aga

I run servers for one of the biggest open source multiplayer games on github. (tgstation/tgstation) Everybody asks why we don't do cloud, and time and time again i have to point out that the fastest per-thread cpu on ec2 costs more per month then our rented bare metal server, that benchmarks as faster per thread, and has 3x the bandwidth we need, included in the price!. Even on a cpu level, the obsession with intel """enterprise""" cpus is leaving money on the table. "but what about web stuff, surely that could go on the cloud!" the best cpus to run (mostly) single threaded game servers right now come with 8 to 16 cores, and we aren't running that many game servers in each region we target, so what else are we gonna do with those spare cores but load up ansible managed docker swarms to handle the webstuff? Notice how I haven't even needed to get to the egress cost to point out how senseless going to the cloud can be.

stewartmcgown 5y ago
I get very happy seeing people run Docker Swarm in production. we need a community!
- TheFlyingFish 5y ago
  I run Docker Swarm on my homelab, but I honestly wouldn't touch it for production because it's lacking features that I find critical and doesn't show any signs of developing them soon. For example, Swarm secrets can only be exposed as files, not as environment variables. You can argue this is more secure because file permissions are more granular than env vars, but IMO that's a silly argument in a container context because containers are almost always single-user to begin with. Moreover, the vast majority of containerized applications expect their secrets in env vars, so you have to resort to fragile entry point wrappers if you want to make use of Swarm secrets.
  - MrStonedOne 5y ago
    honestly the biggest failure of swarm secrets is the inability to change them while things are using them. automating secret usage across containers that are deployed via ansible scripts gets annoying in that situation.

stewartmcgown 5y ago

I get very happy seeing people run Docker Swarm in production. we need a community!

TheFlyingFish 5y ago
I run Docker Swarm on my homelab, but I honestly wouldn't touch it for production because it's lacking features that I find critical and doesn't show any signs of developing them soon. For example, Swarm secrets can only be exposed as files, not as environment variables. You can argue this is more secure because file permissions are more granular than env vars, but IMO that's a silly argument in a container context because containers are almost always single-user to begin with. Moreover, the vast majority of containerized applications expect their secrets in env vars, so you have to resort to fragile entry point wrappers if you want to make use of Swarm secrets.
- MrStonedOne 5y ago
  honestly the biggest failure of swarm secrets is the inability to change them while things are using them. automating secret usage across containers that are deployed via ansible scripts gets annoying in that situation.