On Sun, 16 Aug 2020 07:26:36 -0400, Rich Freeman wrote: > > Going OT here, but why do you dislike Docker? I've only recently > > started using it, so if there are any major, or otherwise, drawbacks, > > I'd like to know before I get too entwined in their ecosystem. > > It has been a while since I've tried it, but networking with Docker is > a PITA. Just having it use DHCP/DNS like any normal host isn't an > option, and it seems like you have to stick some kind of reverse proxy > in front of everything.
That makes sense, although I'm running a reverse proxy anyway as I have different services on different hosts behind a single public IP address. I saw a systems using Traefik last week. Traefik offers some sort of auto-discovery to handle this sort of thing. > I can see how it makes sense at scale. However, if you just need one > instance of something, it is just way more complexity than you need. Yes, it's more work for a single container, but once you start running more there's very little extra work involved. > I personally use nspawn to run my containers, with a network > namespace. They just have their own MACs, run DHCP, and generally > work like any VM minus the memory use. I've used nspawn in the past and it worked well for what I needed, maybe I need to revisit it. > But, perhaps I just need to drink more of the kool-aide and it will > click some day. All I want is to be able to type a.b.com in my > browser and have it display the service I just started up. With > nspawn that is just a matter of a few lines in dhcpd.conf and my BIND > config. That seems to be what Traefik promises when used with Docker, make that Kool-Aid a double :) -- Neil Bothwick Windows Error #09: Mouse not found. Press mouse button to continue.
pgpOcEUk7gaEQ.pgp
Description: OpenPGP digital signature
