New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"lando init pantheon" fails when files in ~/.ssh have unexpected ownership #1203

benjifisher opened this Issue Sep 19, 2018 · 2 comments


None yet
2 participants
Copy link

benjifisher commented Sep 19, 2018

Tell us about your setup

What is your lando version and operating system?

Lando v3.0.0-rc.1, macOS 10.13.6

Tell us about your .lando.yml


Tell us about the command you were running

$ lando init pantheon
? Choose a Pantheon account
? Which site? mysite

Tell us about the error you got

I hope this is enough:

lando init pantheon -- -vvv
verbose: /Applications/,--project-name,landoinitmysite,--file,/Users/bfisher/.lando/util/util-mysite-1.yml,up,-d,--no-recreate,--remove-orphans,util finished with code 0
debug: Emitting event post-engine-start
debug: Event post-engine-start has 0 listeners
debug: Emitting event pre-engine-up
debug: Event pre-engine-up has 0 listeners
debug: Retrieved from memcache with key engineup
debug: Emitting event post-engine-up
debug: Event post-engine-up has 0 listeners
debug: Emitting event pre-engine-run
debug: Event pre-engine-run has 0 listeners
Scanning /user/.ssh for keys...
chown: changing ownership of '/user/.ssh/.config.un~': Operation not permitted
debug: Logging metrics data {"devMode":false,"nodeVersion":"v10.4.1","mode":"cli","os":{"type":"Darwin","platform":"darwin","release":"17.7.0","arch":"x64"},"product":"lando","version":"3.0.0-rc.1","message":"Scanning /user/.ssh for keys...\r\nchown: changing ownership of '/user/.ssh/.config.un~': Operation not permitted\r\n","action":"error","created":"2018-09-19T22:19:17.376Z"}

Tell us generally about your bug

I tried to create a Lando site using lando init pantheon. Because of a file in ~/.ssh owned by root, the command failed.

To reproduce:

sudo touch ~/.ssh/.config.un~
mkdir foo
cd foo
lando init pantheon

Tell us more

Could better documentation have prevented this issue? if so what should we change?

No, but there is a related issue that caused me some headaches. It would have helped me if the documentation of lando init emphasized the difference between lando init pantheon and lando init --recipe=pantheon.

Does this bug prevent you from using lando?

No. I was able to remove the offending file and repeat the command.


This comment has been minimized.

Copy link

pirog commented Sep 20, 2018

@benjifisher thanks for posting this issue. worth pointing out the init differences are explained pretty well over here

@pirog pirog added this to the RC1 milestone Nov 28, 2018

@pirog pirog self-assigned this Nov 28, 2018

@pirog pirog modified the milestones: 3.0.0-rc.2, 3.0.0-rc.3 Jan 23, 2019

@pirog pirog modified the milestone: 3.0.0-rc.3 Jan 31, 2019

pirog added a commit that referenced this issue Feb 2, 2019


This comment has been minimized.

Copy link

pirog commented Feb 2, 2019

Alright, we've got some ownership handling dialed in here now!

@pirog pirog closed this Feb 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment