It's really nice to have the common interface and tools both on dev and prod. If I didn't wrap these binaries in Docker I'd be wrapping them in upstart scripts, systemd config, chef scripts or .deb packages.
All of these layers are a burden. Docker is simply more modern, easier, and has a great API, and tools for packaging, running and monitoring a program.
Why not Docker for everything?
(No, I can't replace these with a couple of command-line Unix tools just yet.)
Same as JARs or C/C++ binaries. You can ship the compiled product to the target runtime and expect it to launch and run as-is.
Languages with an interpreted nature require containers to also ship an additional runtime, plus a dependencies mechanism.
Which is amazing and frustrating since it exposes the inability of other languages to operate in such a simple environment. Even languages like Rust, C and C++ aren't able to do this reliably all the time, with the results being highly dependent on libraries and platforms of choice.
the Rust ppl are looking toward static linking [links]...
https://internals.rust-lang.org/t/static-binary-support-in-r... https://github.com/rust-lang/rust-buildbot/issues/24
Even if the isolation isn't of much value, Docker is still useful as transport and storage. Getting back to the shipping container metaphor, it's easier to move things around if they are all the same. And Docker containers are a pretty good way to do that with code.