|
|
|
|
|
|
by boloust
1418 days ago
|
|
|
It seems like your view is informed from a cursory reading of the docs, rather than any first-hand experience. Docker produces OCI images, there's no need to "export them" in that format. So since Kubernetes can run any OCI image, and Docker images are OCI, Kubernetes supports running Docker images out of the box. The documentation you linked to is if you wanted to swap out the container runtime Kubernetes is using, not if you just want to run a Docker image. |
|
|
Fun though personal attacks are, you would be wrong; I have done all of this, including using docker to build images and k8s to run them.
> Docker produces OCI images, there's no need to "export them" in that format.
Sure.
> So since Kubernetes can run any OCI image, and Docker images are OCI, Kubernetes supports running Docker images out of the box.
...Kubernetes supports running OCI images out of the box. That they were built by docker does not make them docker images, any more than building a Windows program with MinGW creates a "Linux program" just because it was compiled on Linux. If you use docker to build an OCI image and then create a container from that image in a stock k8s cluster, you are not creating a docker container, you are creating a (most likely) containerd container from an OCI image.
> The documentation you linked to is if you wanted to swap out the container runtime Kubernetes is using, not if you just want to run a Docker image.
Yes, I was attempting to charitably include the case where your claim could still be correct. (Since by adding the docker runtime you can create a k8s cluster that creates docker containers.)