#Docker on mac performance for mac os#
#Docker on mac performance for mac#
#Docker on mac performance install#
#Docker on mac performance full#

Randy is the lead maintainer of the DDEV project.Also See: windows 10 19h2 build 18362.10013 Thanks to Randy Fay for reviewing this blog post. I definitely foresee myself migrating project sites to Colima over the next few weeks. I haven't run into any issues, and Colima-based sites seem a bit snappier (especially when DDEV's Mutagen functionality is enabled). Basically, the 'context' refers to which Docker provider the Docker client will route commands to. Regardless, I use docker context show to verify that either the 'default' (Docker Desktop for Mac) or 'colima' context is in use. Technically, starting and stopping Colima isn't necessary, but the ddev poweroff command when switching between the two contexts is.Īlso - recent versions of Colima revert the Docker context back to 'default' when Colima is stopped, so the docker context use default command is no longer necessary.

ddev start (on an existing project I had previously set up while running Docker Desktop for Mac).When colima start is run, it automatically switches docker to the 'colima' context.

#Docker on mac performance for mac#

'default' is the traditional Docker Desktop for Mac containers.

docker context use default - this is the command I alluded to above that tells the Docker client which containers we want to work with.

Switching between a Colima DDEV project and a Docker Desktop for Mac DDEV project (It is recommended to enabled DDEV's mutagen functionality to maximize performance).

Next, I spun up a new Drupal 9 site via ddev config, ddev start, etc.

After the first time, only colima start is necessary.

Next, I started Colima with colima start -cpu 4 -memory 4 The -cpu and -memory bits only have to be done once.

#Docker on mac performance install#

To get started, I first installed Colima using Homebrew brew install colima.Installing Colima alongside Docker Desktop for Mac and starting a fresh Drupal 9 site Once I understood the basics, it's not too difficult to switch between. I currently have some local projects using Docker and some using Colima. If you choose to keep using both Colima and Docker Desktop then when issuing docker commands from the command line, you'll need to first specify which containers we want to work with - Docker or Colima.

#Docker on mac performance full#

Full installation instructions can be found on the DDEV docs site. If you want to go 100% pure Colima and you uninstall Docker Desktop for Mac, you'll need to install and configure the Docker client independently. The docker client is used on the command line to connect to the installed Docker provider (Colima or Docker Desktop for Mac, in this context). The reason for this (as I understand it) is because Colima uses the open-source Lima project for managing its containers and volumes (the latter being where DDEV project databases are stored).įor those of us that are casual Docker users (outside of DDEV), one confusing bit is that we still need the open-source docker client installed - which is installed by default with Docker Desktop for Mac. The easy fix is to first export your database, then start Colima, then import it. In other words, if you have an existing project up-and-running in DDEV, then add Colima, then restart the project, your database won't be found. I say almost for one reason, as any existing DDEV projects will need to have their databases reimported. Based on the fact that Colima is open-source, Docker Desktop's new license terms, and the apparent performance gains of using Colima it seems like a no-brainer to give it a spin.įirst off, it's almost a drop-in replacement for Docker Desktop.

#Docker on mac performance for mac os#

Back in March, 2022, the DDEV team announced support for Colima, an open-source Docker Desktop replacement for Mac OS X.