Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
BUG: Passphrase protected ssh key not being loaded #1143
Tell us about your setup
v3.0.0-beta17 on macOS High Sierra 10.13.6
Tell us about your
name: multisite recipe: drupal8 compose: - compose.yml config: webroot: web via: nginx php: '7.1' xdebug: true tooling: build.sh: service: appserver description: Execute build.sh cmd: - ./build.sh codeception: service: appserver description: Run codeception cmd: - ./vendor/bin/codecept phpcs: service: appserver description: Run phpcs cmd: - ./vendor/bin/phpcs codesniff: service: appserver description: Run code sniffer with default config cmd: - ./vendor/bin/phpcs - "--standard=phpcs.xml" phpcbf: service: appserver description: Run phpcbf cmd: - ./vendor/bin/phpcbf codefix: service: appserver description: Run code autofix cmd: - ./vendor/bin/phpcbf - "--standard=phpcs.xml" theme-build: service: node description: Builds themes css files cmd: true sync.sh: service: appserver description: Execute sync.sh cmd: - ./sync.sh services: mailhog: type: mailhog hogfrom: - appserver appserver: ssl: true extras: - "/app/extras.sh" overrides: services: environment: WKV_SITE_ENV: lando elasticsearch: type: compose services: image: blacktop/elasticsearch:6.3 command: /elastic-entrypoint.sh elasticsearch ports: - "9200:9200" kibana: type: compose services: image: blacktop/kibana:6.3 environment: KIBANA_ELASTICSEARCH_URL: http://elasticsearch:9200 ports: - "5601:5601" command: /docker-entrypoint.sh kibana node: type: node run: - cd $LANDO_MOUNT/web/themes/custom/defender/ && yarn install db_1: type: mariadb:10.1 portforward: 32001 db_2: type: mariadb:10.1 portforward: 32002 db_3: type: mariadb:10.1 portforward: 32003 db_4: type: mariadb:10.1 portforward: 32004 db_5: type: mariadb:10.1 portforward: 32005 db_6: type: mariadb:10.1 portforward: 32006 db_7: type: mariadb:10.1 portforward: 32007 proxy: mailhog: - mail.lndo.site elasticsearch: - search.lndo.site:9200 nginx: - site1.lndo.site - site2.lndo.site - site3.lndo.site - site4.lndo.site - site5.lndo.site - site6.lndo.site - site7.lndo.site kibana: - kibana.lndo.site:5601 events: post-start: appserver: cd $LANDO_MOUNT && composer install && ./vendor/bin/phpcs --config-set installed_paths /app/vendor/drupal/coder/coder_sniffer/ post-theme-build: node: cd $LANDO_MOUNT/web/themes/custom/defender/ && npm run build
Tell us about the command you were running
Tell us generally about your bug
I tried to use passphrase protected ssh keys. Set the global config according to documentation https://docs.devwithlando.io/config/ssh.html, but the ssh key in question is still not loaded.
Tell us more
My guess is that something from this old commit has been lost. Looks like the variable
Thanks for reporting this, it is a problem I've come across as well. The documentation incorrectly states you need to set
Instead the solution seems to be to set the
As there is no ssh agent you'll be asked for your passphrase every time you do something with that key.
This was referenced
Sep 6, 2018
Can confirm. The documented variable had no effect, my no-passphrase keys were loaded while the others are not.
When I add the above suggestion to my lando config.yml, I get this:
This bug prevents me from using
https://docs.devwithlando.io/config/config.html makes it sound like you can simply use
but I also tried adding editing config.yml per tanc's comment
Do you have to run
The varilable is set:
However my passphrased key still does not appear in the 'Using the following keys:' output when I run
I suspect the issue is this line in load-keys.sh:
Perhaps another set of
I'm on MacOS 10.13.6 running bash 4.4.19(1)-release.
I debugged the above further and found that load-keys.sh is working correctly. The problem is simply that $LANDO_LOAD_PP_KEYS is not set (despite setting it as described above) when that script runs.
@bwood did you do a
I've just been trying this out, here are my steps:
I was then able to specify that key when using ssh from inside a container with something like:
If this was my default key I wouldn't need the
I haven't tried using
I setup the
Now, within the container the /var/www/.ssh/ directory still doesn't hold my protected ssh keys...