Josh Rivers

@cstross@wandering.shop long-arc epic fantasy series which the author has not completed?

@jws@infosec.exchange @mc@toot.houbahouba.de @tailscale@hachyderm.io Thanks for the engagement Jay. In my experience the device limit has been psychological more than real, but it is also a bit self-fulfilling. I’ve got a number of services that I design into subnet router topologies rather than on-TS-net simply because I don’t want to use up my allotment or need to juggle later. I’d gladly pay $5/month for some huge allotment that I’d never use just to keep myself from having a scarcity mindset. If there were a good way to do that that avoided abuse by commercial users, it would be 🧡

@Guillotine_Jones @maxleibman Me too. Kinda just glazed over at the Godfather stuff. Maybe if it had been a West Wing reference?

@cstross@wandering.shop Look! I’ve found a socially beneficial use for AI!

@devxvda God that makes me hot. I’ll be in my bunk.

@rasmus91@fosstodon.org @ggpsv@social.coop @jwildeboer@social.wildeboer.net I also think a lot of the critique of Docker comes from it getting used for production hosting scenarios, which was never the desired outcome. We are stuck on the timeline where Google squashed Docker Swarm with ‘free’ k8s (which is so complicated you need to pay a hyperscaler to host if for you). I suspect a production-hardened Docker hosting ecosystem would be both easy and incredible, but nobody wanted to pay to develop and license that. Podman is probably better for containerizing apps and daemons on a Linux desktop, assuming you know how to do it right or someone is packaging it for you. Poorly managed Docker ‘servers’ using copypasta compose files are probably suboptimal as well. But there is a real learning curve to containerization and not everyone has the enthusiasm to mount it. Docker makes that curve a whole lot less steep.

@ismh86@eworld.social I had that go wrong on last update. About a week later the controls popped back in and worked again. It’s a pretty gross little “it just doesn’t work” bug.

@rasmus91@fosstodon.org @ggpsv@social.coop @jwildeboer@social.wildeboer.net I’ve got a lot of answers here and I won’t cover all of them, but the “just works” aspect is a good take. Docker is a developer tool that makes a lot of things (packaging, process isolation, persistence, network isolation, service location, process supervision, remote administration, secure distribution) all work without the user really needing to understand them. Beyond Docker, Docker Desktop has some black magic that makes it work and work easily in I.T. environments which would make a VM-like solution a nightmare. I don’t think Docker is ‘better’ but I have a lot of peers that have enough trouble learning containers with Docker and would be lost in the woods for something more complicated. If I had a choice of getting folks to use containers in Docker vs not using containers, I’d choose Docker without reservation.

@ggpsv@social.coop @rasmus91@fosstodon.org @jwildeboer@social.wildeboer.net I haven’t spent as much time as I’d like with podman, but I have run into fidelity issues with other docker replacement components in the past. I’m rather suspicious that podman doesn’t handle, say, restart-policy with the same seamlesssness. I also suspect that you can get the same levels of control and isolation with some level of effort in Docker. If the primary complaint is the socket, there are several ways to secure that. Probably, anyone who understands containers as well as you or I do would benefit from podman, but I doubt rootless podman running from user accounts is a drop in identical replacement for a docker daemon running as root, and many users would stub their toes on the differences.