4 ms·
I think, when people are talking about "using Docker", they're talking about using Docker tooling to build and push/update/pull Docker images (actually OCI imag
by derefr 7y ago
I think, when people are talking about "using Docker", they're talking about using Docker tooling to build and push/update/pull Docker images (actually OCI images) around. They're not really talking about running OCI images "on the Docker daemon container runtime." But to most people, OCI images are "Docker" and if your cloud scheduler/hypervisor can run them then it's "a Docker runtime."
- wokwokwok 7y agoI like to believe most people are sufficiently with-the-plot to appreciate that there is a difference between a "container", "container runtime", "container orchestration" and "docker". No one is seriously confused about "using docker" meaning, oh hey, I run my containers on kubernetes. I have literally never met someone who was confused about this. I suppose some people just stop at "I use docker" and don't know what that means when it hits production... but I'm skeptical they actually think a copy of docker is running out there in prod. ...but to be fair, the parent comment did say that running "docker containers" was mainstream; and fair enough. My point was running containers using docker most certainly is not.
- asadlionpk 7y agoI don't get your point. Isn't docker the default runtime everywhere? k8s uses docker internally, by default. So containers are most certainly run in prod using docker (to be specific docker daemon), are they not?
- jjeaff 7y agoDocker daemon is the default runtime for k8s and k8s is most definitely being used in lots of production environments.