3 ms·

I think you already answered the question. You don't need to introduce docker cli, docker daemon, a container registry, etc. Not saying theres anything wrong wi

• danenania 6y ago
  Exactly. The fewer moving parts, the better. Even if you still use Docker, a container wrapping a single binary is simpler than a container with dependencies and source files. It’s also good for closed source use cases (blasphemy, I know).
• 205g0 6y ago
  Ok, the Docker client stuff is not always exciting but once you want to deploy something small, say, an app server, a DB and something like nginx or Traefik you need some orchestrator, eg k8s and then you need again images. If you prefer containerd over Docker also good. What I am saying is which orchestration and deployment system does favor single executables atm and has a huge ecosystem? You still need to create images and do double the work. I like real binaries like Go creates but repackaging the run-time doesn't sound like a sophisticated idea but rather making the black box even bigger. As a sibling said, for client side/3rd party apps, yeah this might be a nice-to-have but this space has rather other challenges.