[Pirate-of-SV]

What you say is true for container images and putting an ELF binary as the only file in an image doesn't make much sense if your only purpose is to run it without any other requirements.

However don't forget that Docker also gives the user an interface for running processes in a namespace and cgroup!

[stephenr]

So does systemd, which, fucking abysmal community engagement approach aside, is technically a lot more usable and reliable than Docker.

[ivanilves]

Docker IMO does the packaging thing very well.

I agree that for the bare Golang application systemd will be enough.

But what will you do with Java and (OMG!) Ruby, NodeJS applications?

For lots of stuff out there Docker packaging capabilities are vital!

[stephenr]

What will I do? Install their dependencies.

People have been running servers and installing software for a long time before Docker came around, and will be for a long time after it's flavour of the month appeal wears off.

[mschuster91]

> What will I do? Install their dependencies.

Good luck when you want to have multiple projects installed on a single server.

[stephenr]

rbenv is a thing that exists.

npm already installs dependencies locally by default.

I already generally avoid Java apps, for bigger reasons than packaging, but setting a custom $CLASSPATH for the JVM to load your dependencies isn't really that difficult.