potiuk commented on code in PR #27844: URL: https://github.com/apache/airflow/pull/27844#discussion_r1030165407
########## CONTRIBUTORS_QUICK_START.rst: ########## @@ -50,7 +50,7 @@ Local machine development If you do not work with remote development environment, you need those prerequisites. -1. Docker Community Edition (you can also use Colima, see instructions below) +1. Container runtime: Docker Community Edition (recommended), Colima. Review Comment: Correct. Runtime is docker. In our case what we use from Colima is the replacement of Docker Desktop VM management and integration (mounts, sockets and the like). But we actually still use docker runtime. What Colima does, it starts Lima VM behind the scenes automatically as needed and under the hood it still uses the same docker runtime. We do not use `containerd` runtime (that Colima also supports). For that we would have to use https://github.com/containerd/nerdctl to run the commands.. Those are subtle differences that the users are not even aware of but we should be more precise, I think, in terminology :D. The `docker` is term that has been used for everything - Docker Runtime, Docker CLI, Docker Engine, recently Docker Desktop - all those are different and pretty much each of them is replaceable (but only Docker Desktop requires an alternative because only Docker Desktop has this - prohibitive for many companies - licence). We are in a process of unbundling of those meanings, and I think it's good to be precise. Colima in our case is used to replace "Docker Desktop" part while all the other "docker" parts remain (but Runtime and Engine are in Colima-managed VM). BTW. Funny thing is that Colima on Linux stil uses Docker Engine and Runtime - but they are installed in the Lima VM. So in a way you get rid of the engine (but only on a Host). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
