-
Notifications
You must be signed in to change notification settings - Fork 102
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
Support for GCE OS Login #208
Comments
@rdhyee rsync is actually provided by the I'm not sure this is something I can change fairly quickly as I don't have a lot of cycles nowadays. However, I'd be happy to give pointers or review a PR if you're willing to take a crack at it. |
Google documentation steers people towards using OS Login: So, I think it is important to implement support for it. I ran into the same issue that was reported here, and if this issue is not resolved, that would prevent us from using @Temikus Could you outline in a bit more detail what needs to change in the |
The most interesting part that I discovered today is that it works with the same Vagrantfile in centos 7 and doesn't work in ubuntu 16 or ubuntu 18. All this was tested in GCP. |
Are there any plans to review this issue? it's very painful not to be able to use it with GCP and Ubuntu OS family. |
@konstantin-recurly As I said in #208 (comment) this is a free time project and I don't have a lot of bandwith to implement this. However, if you'd like to contribute I'm happy to review PR's and give pointers. |
The current support for SSH offered by this provider makes use of adding SSH keys in GCE metadata. I'm inquiring about whether there's any interest in supporting the alternative way of accessing GCE instances: OS Login.
When I naively turned on OS Login, Vagrant was able to ssh into the instance but failed when trying to
rsync
with the instance. In myVagrantfile
, I had the configuration lineto match the username key for the SSH key configured in OS Login
Apparently, it seems that the rsync action assumes that there would be a group with the same name as the username -- and this assumption is not correct when using OS Login.
The text was updated successfully, but these errors were encountered: