Skip to content
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

"ControlPath too long" on git push #127

Open
dr0pdb opened this issue Apr 1, 2020 · 1 comment
Open

"ControlPath too long" on git push #127

dr0pdb opened this issue Apr 1, 2020 · 1 comment

Comments

@dr0pdb
Copy link

dr0pdb commented Apr 1, 2020

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
Copy link

jpc commented Oct 5, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants