I don't think that's very verbose. The dockerfile I was using to build the app basically grabbed a specific version of all the deps and ./configure && make ins

I don't think that's very verbose. The dockerfile I was using to build the app basically grabbed a specific version of all the deps and ./configure && make install'ed each one. I'm completely onboard with the idea of reproducible builds. > The thing is docker is huge and bloated; is far from secure, and will probably stay that way for the foreseeable future It would be a mistake to fully associate container workflows with docker itself. https://github.com/genuinetools/img https://github.com/genuinetools/img + https://github.com/opencontainers/runc https://github.com/opencontainers/runc can be used to provide almost the same workflow as docker, without using docker itself. You could also use the '-f docker' option the post talks about with runc to run the resulting image in an unprivileged container.