hasura / gitkube

Build and deploy docker images to Kubernetes using git push
Apache License 2.0
3.81k stars 207 forks source link

"ControlPath too long" on git push #127

Open dr0pdb opened 4 years ago

dr0pdb commented 4 years ago

Hi,

I have been trying to setup gitkube for my application. The k8s cluster is running on AWS EKS. Gitkubed has been deployed as a LoadBalancer.

I've created the remote.yaml and configured the git remote. When I run git push leadsvc master, I get the following error:

ControlPath too long ('/home/srv_twry/.ssh/ssh-default-leadsvc@a4d730ced73e911ea95fe0ab91861530-1070077455.us-east-1.elb.amazonaws.com:22' >= 108 bytes)
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Anyway to fix this? Where can I save space in order to fit it in the limit?

jpc commented 2 years ago

You can add ControlPath ~/.ssh/%C in your .ssh/config which will use a hash instead of the full connection information. A small downside is that the control socket names are gibberish but the upside is that the length is fixed so you won't run into the path length problem.