github on AzureML

[hannahbrown7]

Not an issue that needs to be resolved as part of precip rediagnosis, but more a lesson for future used of Azure when setting up a project in a new resource group.

Code in cloned github repos are shared across compute instances but github access only available from the instance that the repository was originally cloned on. Creating a github access compute instance may be a good way of managing this.

[stevehadd]

You can enable git push/pull access on multiple compute instances if youn either copy across the SSH keys to multiple compute instances, or you create multiple SSH keys, but either option is messy. Really we'd like GH repos ( or repos generally) to be handled as part of the core AzML functionality like compute or datasets (i.e. have their own little icon on the main page), so that users don't have to fiddle with git details all the time.

[stevehadd]

A related or possibly the same issue I have now experienced. When I tried to access a GH repo cloned on compute instance A ands then try to run git commands on compute instance B, I get the following error:

fatal: detected dubious ownership in repository at /path/to/repo

So this looks like it is not recognising me as the same user on different VMs, despite this being a shared code directory. So I think its probably a user permissions thing not being set correctly for different compute instances (VMs under the hood). Something we can feed back to microsoft at some point.

Aled suggested possibly running the clone command with the following flag to get around this (not yet tried)

git clone repo@git --shared

doc link