title: Lando: exec error with environment variables
body: <p>I'm using <a href="https://lando.dev" rel="nofollow noreferrer">Lando</a> (v3.0.0-rc.21 on Windows 10 Enterprise) and trying to set up an environment variable on container creation in my <code>.lando.yml</code>:</p>
  
  <pre><code>services:
    appserver:
      type: ruby # the same for php, but didn't tested other types
    run:
      - export SOMENAME=somevalue
  
  tooling:
    test:
      cmd: export SOMENAME=somevalue
      service: appserver
  </code></pre>
  
  <p>It looks like the command is not recognized while Lando starts since it throws:
  <code>OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "exec: \"export\": executable file not found in $PATH": unknown</code></p>
  
  <p>The very same error occurs on <code>lando ssh -c "export SOMENAME=somevalue"</code> or adding it as a command into tooling section in <code>.lando.yml</code> (see above) and then running <code>lando test</code>.</p>
  
  <p><strong>However</strong>, running the same command from <code>lando ssh</code> after lando has started works as it should:</p>
  
  <pre><code>lando ssh
  www-data@81bd623b9c3a:/app$ export SOMENAME=somevalue
  www-data@81bd623b9c3a:/app$ printenv SOMENAME
  somevalue
  www-data@81bd623b9c3a:/app$
  </code></pre>
  
  <p>Is this a Lando bug? Or some (which?) shell commands should be called somehow different?</p>