Getting Started with Lando - testing a fresh Drupal 8 Umami site

Umami demo profile running on Lando for Drupal 8
Testing out the new Umami demo profile in Drupal 8.6.x.

I wanted to post a quick guide here for the benefit of anyone else just wanting to test out how Lando works or how it integrates with a Drupal project, since the official documentation kind of jumps you around different places and doesn't have any instructions for "Help! I don't already have a working Drupal codebase!":

  1. Install Docker for Mac / Docker for Windows / Docker CE (if it's not already installed).
  2. Install Lando (on Mac, brew cask install lando, otherwise, download the .dmg, .exe., .deb., or .rpm).
  3. You'll need a Drupal codebase, so go somewhere on your computer and use Git to clone it: git clone --branch 8.6.x lando-d8
  4. Change into the Drupal directory: cd lando-d8
  5. Run lando init, answering drupal8, ., and Lando D8.
  6. Run lando start, and wait while all the Docker containers are set up.
  7. Run lando composer install (this will use Composer/PHP inside the Docker container to build Drupal's Composer dependencies).
  8. Go to the site's URL in your web browser, and complete the Drupal install wizard with these options:
    1. Database host: database
    2. Database name, username, password: drupal8

At the end of the lando start command, you'll get a report of 'Appserver URLs', like:

APPSERVER URLS  https://localhost:32771                        

You can also get this info (and some other info, like DB connection details) by running lando info. And if you want to install Drupal without using the browser, you could run the command lando drush site-install -y [options] (this requires Drush in your Drupal project, which can be installed via composer require drush/drush).

It looks like Lando has a CloudFlare rule set up that redirects * to, and the https version uses a bare root certificate, so if you want to access the HTTPS version of the default site Lando creates, you need to add an exception to your browser when prompted.

Note that Little Snitch reported once or twice that the lando cli utility was calling out to a metrics site, likely with some sort of information about your environment for their own metrics and tracking purposes. I decided to block the traffic, and Lando still worked fine, albeit with a few EHOSTDOWN errors. It looks like the data it tried sending was:


Nothing pernicious; I just don't like my desktop apps sending metrics back to a central server.

Docker Notes

For those who also use many other dev environments (some of us are crazy like that!), I wanted to note a few things specific to Lando's Docker use:

  • Lando starts 3 containers by default: one for MySQL, one for Apache/PHP, and one for Traefik. The Traefik container grabs host ports 80, 443, and 58086.
  • Running lando stop doesn't stop the Traefik container, so whatever ports it holds won't be freed up until you run lando poweroff.
  • If another running container (or some other service) is already binding to port 80, lando start will find a different free port and use that instead (e.g.


Any similar directions for DrupalVM with Docker? :)


  1. Ensure you have Docker for Mac/Windows/etc. installed.
  2. docker run -d -p 80:80 -p 443:443 --name=drupalvm --privileged geerlingguy/drupal-vm
  3. docker exec drupalvm install-drupal 8.x-dev
  4. Go to http://localhost/

What is your opinion about lando vs ddvev ? Which one will make it in the future ?

Awesome to see you taking Lando for a spin Jeff! If anyone has questions about using the project, hit us up on Slack ( or dive into the issue queue on Github. You can turn metrics tracking off in your `~/.lando/config.yml` so that it stops trying to phone home to the metrics tracker, though we definitely appreciate the data we get from the service. See the example config file in the root of the project and just flip the true to a false to handle that.

You can also run with the proxy off if you want by similarly mucking with the config.yml file. Happy local deving!

You can turn metrics tracking off in your ~/.lando/config.yml so that it stops trying to phone home to the metrics tracker, though we definitely appreciate the data we get from the service.

Thanks for that, will do so I don't keep getting errors in the console :)

Another thing worth noting about the Traefik container is it will be restarted automatically when Docker Engine is restarted. Dev machine or Docker Engine restarts can put the container back online w/o the end user realizing it. This can become an issue if you happen to be working on various docker-based projects.