It should be possible to opt out of mounting `/var/www` as a named mount since it can mess up certain containers such as adminer

[codebymikey]

I have the following service, which uses /var/www/html to serve its codebase:

services:
  adminer:
    api: 3
    type: lando
    ssl: true
    sslExpose: false
    portforward: false
    meUser: adminer
    services:
      image: adminer:5.3.0-standalone
      command: entrypoint.sh docker-php-entrypoint php -S '[::]:8080' -t /var/www/html
      user: root
      ports: ['8080']
      environment: []

However because lando automatically mounts /var/www to the home, it makes updating difficult as it keeps the previous codebase whenever the image is updated, such that if you later switch to 5.4.0, it'll still serve the 5.3.0 codebase assets.

See

core/builders/_lando.js

Line 116 in 4d469f7

`${dataHome}:/var/www`,

It'd be useful if the mount could be opted out from, or the default /var/www home directory can be overridden to something else to avoid the conflict.