@thatguyoverthere @Moon didn't docker start as something like vagrant? reproducible development environments because things already were quite bad in terms of portability. turns out that making it easier to write unportable software doesn't make things better..

@bonifartius @thatguyoverthere it was always meant as a production deployment thing in addition to being used for reproducible build environments.

@Moon @thatguyoverthere ok, maybe i got that mixed up :)

@bonifartius @Moon Well I'd say lxc had uses outside of strictly development, but yeah docker started as just kind of an abstraction layer over lxc that made it easier to use. I think making unportable code more portable was more of a side effect of containerization, but I agree docker making it easy has only made the problems worse.

@thatguyoverthere @bonifartius it's an abstraction over linux containers not lxc proper. linux containers aren't even strictly a first class citizen of the linux kernel from what I can tell they are a collection of kernel features that can namespace parts that, when orchestrated, act like an entire namespaced kernel.

lxc containerizes the entire OS including userland, each container has its own init manager like systemd or openrc or something, and is multiuser and multiprocess. Docker has one user, and one process that is directly launched inside the container without any sort of init manager.

@thatguyoverthere

And the really underlying problem (that continue to make things worse) is that people are lazy and ignorant. And the explosion of more "developers" (doubling every 5 years or so) has only slowed a little bit lately, and we are in a constant shock of "no experience" everywhere.

@bonifartius @Moon