lando / gitpod

Lando

A Liberating Dev Tool For All Your Projects

The local development and DevOps tool trusted by professional developers across the galaxy.

Free yourself from the mind-forged manacles of lesser dev tools. Save time, headaches, frustration and do more real work.

learn more | what is it good for? | wait, doesn't docker compose do this?

Support Lando

Lando is and always will be FREE and OPEN SOURCE. As such it relies on generous contributions from its community to fund its development. Join our list of list of great sponsors! by contributing.

GitHub Sponsors | Patreon | OpenCollective

Documentation

Getting Started

Introduction | CLI Usage | Installation

Recipes

Backdrop | Drupal 6, 7, 8, 9, and 10 | Joomla | Lagoon | Laravel | LAMP | LEMP | MEAN | Pantheon | Platform.sh | WordPress

Services

Apache | Compose | dotnet | Elasticsearch | Go | MailHog | MariaDB | MySQL | MSSQL | nginx | Node | PHP | PhpMyAdmin | Postgres | Python | Redis | Ruby | Solr | Tomcat | Varnish

Advanced Configuration

Landofile | Recipes | Services & Build Steps | Tooling | Proxy & Nice Url Routing | Environment | Events & Automation | Experimental | Networking | Performance | Release Channels | SSH Keys | Global Config

Help, Troubleshooting & Support

Guides and Tutorials | Examples | Known Issues | Accessing Logs | GitHub Issue Queue | Slack Channel | YouTube Videos

Engage

Contribute to the Project | Join the Alliance | Events and Meetups | Blog | Follow on Twitter

Security Issues

If you have discovered a security issue with Lando, please contact the Lando Security Team directly at [email protected]. We manage security issues separately in a private repository until the issue has been resolved. Even if you're not sure if it's a security problem, please contact the security team before filing an issue, blogging, or tweeting about it.

Other Resources

• Mountain climbing advice

gitpod's Issues

Command `lando pull` requests password

Hey there,

I'm trying to use Lando and Gitpod to sync with a repo on Pantheon. I've pulled the code to GitHub so I can run GitPod, but I need to get the database and files from Pantheon... I used the command lando pull (I've got it set up in the .lando.yml to not pull code) and was first prompted for a machine token (no problem) and then for a password (for the local environment, I'm pretty sure).

gitpod /workspace/PROJECT_NAME (master) $ lando pull
? Enter a Pantheon machine token [hidden]
Attempting to login via terminus...
 [notice] Logging in via machine token.
Logged in as [email protected]
Verifying that you have access to PROJECT_NAME...
 ------------------ -------------------------------------------------------------------------------------------- 
  ID                 ...redacted...
 ------------------ -------------------------------------------------------------------------------------------- 
Access confirmed!
Pantheon LOCKR setup
[e-mail]'s password: 

I've tried nothing (just enter), admin, YES, and my pantheon password (just in case), all to no avail. Do you have any idea what the user password is for this environment???

Lando / Lagoon / Gitpod permission woes

Hi - I'm trying to get the Lando+Lagoon integration running in GitPod, but hitting a stumbling block in the php image permissions

lando start reports a set of chown errors on first run:

Creating drupal9base_cli_1 ... done
Creating drupal9base_php_1 ... done
chown: unknown user/group user:/home
chown: unknown user/group user:/home
chown: unknown user/group user:/home
chown: invalid group: 'user:/home'
chown: invalid group: 'user:/home'
chown: invalid group: 'user:/home'
Installing dependencies from lock file (including require-dev)
...

It appears to start, but then the correspondence between php and nginx fails - so every request errors out - and yes, even if Drupal is installed...

php_1        | ERROR: Unable to open primary script: /index.php (No such file or directory)

Looking at the lando logs output:

php_1        | 
php_1        | userperms 06:49:38.INFO  ==> Symlinked users .gitconfig.
php_1        | userperms 06:49:38.INFO  ==> This is a alpine container
php_1        | userperms 06:49:38.INFO  ==> user-perms.sh kicking off as user uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)
php_1        | userperms 06:49:38.DEBUG ==> Lando ENVVARS set at
php_1        | userperms 06:49:38.DEBUG ==> 
php_1        | userperms 06:49:38.DEBUG ==> ========================================
php_1        | userperms 06:49:38.DEBUG ==> LANDO_WEBROOT_USER      : user
php_1        | userperms 06:49:38.DEBUG ==> LANDO_WEBROOT_GROUP     : user
php_1        | userperms 06:49:38.DEBUG ==> LANDO_WEBROOT_UID       : 
php_1        | userperms 06:49:38.DEBUG ==> LANDO_WEBROOT_GID       : 
php_1        | userperms 06:49:38.DEBUG ==> LANDO_HOST_UID          : 33333
php_1        | userperms 06:49:38.DEBUG ==> LANDO_HOST_GID          : 33333
php_1        | userperms 06:49:38.DEBUG ==> ========================================
php_1        | userperms 06:49:38.DEBUG ==> 
php_1        | userperms 06:49:38.INFO  ==> Making sure correct user:group (user:user) exists...
php_1        | userperms 06:49:38.INFO  ==> Remapping ownership to handle docker volume sharing...
php_1        | userperms 06:49:38.INFO  ==> Resetting user:user from : to 33333:33333
php_1        | userperms 06:49:38.INFO  ==> user:user is now running as uid=33333(user) gid=33333(user) groups=33333(user),33333(user)!
php_1        | userperms 06:49:38.INFO  ==> And here. we. go.
php_1        | userperms 06:49:38.INFO  ==> Doing the permission sweep.
php_1        | lando 06:49:38.INFO  ==> Lando handing off to: /sbin/tini -- /lagoon/entrypoints.sh /usr/local/sbin/php-fpm -F -R
php_1        | [WARN  tini (98)] Tini is not running as PID 1 and isn't registered as a child subreaper.
php_1        | Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
php_1        | To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
php_1        | [24-Mar-2022 06:49:38] NOTICE: fpm is running, pid 99
php_1        | [24-Mar-2022 06:49:38] NOTICE: ready to handle connections
php_1        | userperms 06:49:47.INFO  ==> Symlinked users .gitconfig.
php_1        | userperms 06:49:47.INFO  ==> This is a alpine container
php_1        | userperms 06:49:47.INFO  ==> user-perms.sh kicking off as user uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)
php_1        | userperms 06:49:47.DEBUG ==> Lando ENVVARS set at
php_1        | userperms 06:49:47.DEBUG ==> 
php_1        | userperms 06:49:47.DEBUG ==> ========================================
php_1        | userperms 06:49:47.DEBUG ==> LANDO_WEBROOT_USER      : user
php_1        | userperms 06:49:47.DEBUG ==> LANDO_WEBROOT_GROUP     : user
php_1        | userperms 06:49:47.DEBUG ==> LANDO_WEBROOT_UID       : 33333
php_1        | userperms 06:49:47.DEBUG ==> LANDO_WEBROOT_GID       : 1000
php_1        | userperms 06:49:47.DEBUG ==> LANDO_HOST_UID          : 33333
php_1        | userperms 06:49:47.DEBUG ==> LANDO_HOST_GID          : 33333
php_1        | userperms 06:49:47.DEBUG ==> ========================================
php_1        | userperms 06:49:47.DEBUG ==> 
php_1        | userperms 06:49:47.INFO  ==> Making sure correct user:group (user:user) exists...
php_1        | userperms 06:49:47.INFO  ==> Remapping ownership to handle docker volume sharing...
php_1        | userperms 06:49:47.INFO  ==> Resetting user:user from 33333:1000 to 33333:33333
php_1        | userperms 06:49:47.INFO  ==> user:user is now running as uid=33333(user) gid=1000(user) groups=1000(user),1000(user)!
php_1        | userperms 06:49:47.INFO  ==> And here. we. go.
php_1        | userperms 06:49:47.INFO  ==> Doing the permission sweep.
php_1        | chown: unknown user/group user:/home
php_1        | chown: unknown user/group user:/home
php_1        | chown: unknown user/group user:/home
php_1        | lando 06:49:47.INFO  ==> Lando handing off to: /sbin/tini -- /lagoon/entrypoints.sh /usr/local/sbin/php-fpm -F -R

It looks like the second run through of the permission sweep in php_1 is where the problem happens.
I'd certainly appreciate any pointers on whether there's anything special at play here, or whether we need to set some additional permissions in the base images.

The source repo/branch is at https://github.com/tobybellwood/drupal9-base/tree/gitpod

To "fix" it in native docker-compose, we can change the user that the nginx container runs as (to 33333 to match the default gitpod uid) and expose the 8080 port (eg in this commit) - but I've no idea how to effect the same in Lando

lando_lagoon_gitpod.txt