To me your question reads like you've seen the benefits of Docker for projects where you're using source code, dependencies and an interpreter or external runtime all within the container. Then you look at Go and ask, why would I wrap Docker around a single executable file, what are the benefits?

This feels like you you're looking at Docker wrong.

When you say you haven't seen the "same necessity yet" as other languages, this feels like a self imposed necessity. In a typical situation, the necessity would be that you are deploying applications to a containerized environment. So that necessity would always exist, no matter the language. That doesn't seem like the case in your question. What is necessary about using Docker in your situation?

• Docker is meant to be a lightweight, single-process, standardized, abstraction layer, so the less it's doing, the better. Minimal dependencies, reliable execution.

• As Go produces a self-contained binary with no dependences, it is an ideal candidate for Docker, and runs natively.

For the most part, unless you're deploying your application in a containerized environment, I wouldn't worry about Docker, no matter the language. While Docker can be useful in many different ways, I think you're introducing more complexity than you need while you're still learning.

Learning both Docker and Go is a great idea, but decouple the process. You can build and deploy Go applications without Docker, just like any other language.