Could you elaborate? I rely heavily on systemd (I don't always run applications on containers), so my usually server on the cloud looks like: a go binary running under systemd. I can't easily reproduce that with Docker. Sure, for other kind of applications it works quite well, and as I said before I do make use of Docker as well, although I don't think it can satisfy my needs as "infra" engineer.
Docker (specifically docker-compose) using containers is an implementation detail. It even used to use VMs on Windows.
You can replicate your prod environment locally with Docker Compose, but then deploy however you want (with or without containers, with or without Kubernetes).
I never use containers in production, but exclusively use them for local dev.
With Docker you have the binary running inside something like Alpine Linux. Services (like Database) are connected through a DNS-discovery agent (like Consul) and this whole shebang is managed through something like Nomad.
They are all Hashicorp products, by the way, and kind of the evolution from Vagrant. (Ps: It's also quite of a heavy learning curve to move to such setups).