52 ms·

Sure docker is not perfect but isn't running docker containers mainstream practice now? I think your response is a bit of exaggeration.

wokwokwok 7y ago
Haha... for production workloads? Definitely not. Docker is a lovely developer tool, but it’s not, in my experience, ever been (even with swarm when that was a thing) suitable for production workloads. Containers: yes. Docker: that’s a container runtime, and definitely not mainstream for production workloads.
- marktangotango 7y ago
  I’ve wondered about this myself. What is the solution? On premise cloud like openstack?
- 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 ago
    I 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 ago
      I 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 ago
    Docker daemon is the default runtime for k8s and k8s is most definitely being used in lots of production environments.
- manigandham 7y ago
  For many people, Docker = container, created using a Dockerfile and deployed to kubernetes or elsewhere, regardless of the actual runtime underneath.
- hermanradtke 7y ago
  Pretty sure Google App Engine runs Docker under the hood. It has been a while since I logged into a GAE machine.
  - dgoog 7y ago
    It absolutely does not - please cite this.
- bsaul 7y ago
  just to make sure i understand what you’re saying : running containers created with the docker tool is ok, and running it with kubernetes is also ok, but actually deploying docker tool on a server to run the container is not. Am i correct ? Care to explain what makes that docker tool/runtime unsuitable for production ?
- raesene9 7y ago
  you're kidding right? Docker runs as the Container Runtime under most Kubernetes clusters (in fact every Kubernetes cluster I've seen). The only other CRIs that are commonly used are CRI-O and ContainerD (which Docker already uses), and last I saw CRI-O was < 10% of the Container runtime market.
- MagicWishMonkey 7y ago
  What is the problem with using a container based approach for production workloads?
- jensvdh 7y ago
  Most of the industry runs Docker containers in production my dude.
pjmlp 7y ago
Around here it is still plain old VMs, thank you very much.
- asadlionpk 7y ago
  Both have their usecases. It just doesn't make sense to carry around a VM image (or build a new VM image on each push) for a fairly simple web app (which is what many work on).
  - pjmlp 7y ago
    Well, that is what application servers are for.

wokwokwok 7y ago

Haha... for production workloads? Definitely not. Docker is a lovely developer tool, but it’s not, in my experience, ever been (even with swarm when that was a thing) suitable for production workloads. Containers: yes. Docker: that’s a container runtime, and definitely not mainstream for production workloads.

marktangotango 7y ago
I’ve wondered about this myself. What is the solution? On premise cloud like openstack?
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 ago
  I 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 ago
    I 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 ago
  Docker daemon is the default runtime for k8s and k8s is most definitely being used in lots of production environments.
manigandham 7y ago
For many people, Docker = container, created using a Dockerfile and deployed to kubernetes or elsewhere, regardless of the actual runtime underneath.
hermanradtke 7y ago
Pretty sure Google App Engine runs Docker under the hood. It has been a while since I logged into a GAE machine.
- dgoog 7y ago
  It absolutely does not - please cite this.
bsaul 7y ago
just to make sure i understand what you’re saying : running containers created with the docker tool is ok, and running it with kubernetes is also ok, but actually deploying docker tool on a server to run the container is not. Am i correct ? Care to explain what makes that docker tool/runtime unsuitable for production ?
raesene9 7y ago
you're kidding right? Docker runs as the Container Runtime under most Kubernetes clusters (in fact every Kubernetes cluster I've seen). The only other CRIs that are commonly used are CRI-O and ContainerD (which Docker already uses), and last I saw CRI-O was < 10% of the Container runtime market.
MagicWishMonkey 7y ago
What is the problem with using a container based approach for production workloads?
jensvdh 7y ago
Most of the industry runs Docker containers in production my dude.

pjmlp 7y ago

Around here it is still plain old VMs, thank you very much.

asadlionpk 7y ago
Both have their usecases. It just doesn't make sense to carry around a VM image (or build a new VM image on each push) for a fairly simple web app (which is what many work on).
- pjmlp 7y ago
  Well, that is what application servers are for.