-
Notifications
You must be signed in to change notification settings - Fork 65
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
wokrspace remote Error: "git must be available and on the PATH" while deploying terraform resource using wokrspace remote #309
Comments
Versions 19.1 and 19.2 of the images appear to be broken. They lack essential system binaries, including the Git binary, which causes the error described in the issue. The 19.0 image seems to be functioning correctly. @turkenf: It looks like the 19.1 and 19.2 images need to be rebuilt to resolve these issues. |
Interesting, that would be unexpected given the small set of changes between v0.19.2 and v0.19.0: v0.19.0...v0.19.2 Looks like just some go dependency bumps for recently published vulnerabilities. I don't see the build process, docker file, base image, etc. changing there. @innersavage if you get a chance, can you share any debugging info you have for finding that the |
@jbw976 I'm not sure what type of debugging you expect :-) You can just pull the image and check it by yourself (like below): As you can see, only couple of binaries are present in the image. Even busybox is missing. Here's the 19.0 for comparison: As you have noticed, nothing changed in the image build process and the changes between the versions shouldn't cause this issue. That's why my best guess is something went wrong in the environment on which the v0.19.1 and v0.19.2 images were built. |
Hello @innersavage, @a936455 Thank you very much for your interest and sharing your findings. My teammate @sergenyalcin has been working on this issue and has created a test image that we think solves the issue. I will share the image with you. If you have time, we would be very happy if you could test and verify it. |
Had a look at that container image, it seemed to have Type Reason Age From Message
---- ------ ---- ---- -------
Warning CannotConnectToProvider 92s managed/workspace.tf.upbound.io cannot get remote Terraform module: error downloading '<GHE URL>': /usr/local/bin/git exited with 128: Cloning into '/tmp/getter268484131/temp'...
warning: templates not found in /usr/share/git-core/templates
git: 'remote-https' is not a git command. See 'git --help'. |
Thank you for sharing @gazal-k, we will look into this 👀 |
The image has |
Hello folks, We have a new version |
Thank you for that. Can't see what changed though 😞 v0.19.2...v0.19.3 |
@gazal-k The issues with the broken versions were unrelated to the provider code, but crept in due to the new build pipeline we use when building and publishing them to the registry. We've ironed out the problems and it should no longer be an issue going forward. |
I am using the terraform-provider to add "github_repository_collaborators" in GitHub organization.
I have done following septs as documented.
Error while deploying: Crossplane beta trace error:
Just for the information few months ago when I have deployed it was working fine.
checked the terraform-provider log. There is nothing.
Error: Can not connect to provider
![image](https://private-user-images.githubusercontent.com/190359923/399738787-b72cface-9665-4feb-b0a4-bbee77830489.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk0MDQ1OTIsIm5iZiI6MTczOTQwNDI5MiwicGF0aCI6Ii8xOTAzNTk5MjMvMzk5NzM4Nzg3LWI3MmNmYWNlLTk2NjUtNGZlYi1iMGE0LWJiZWU3NzgzMDQ4OS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjEyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMlQyMzUxMzJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0xMGMxYzMzMDIxNTNlYzk2MjI5YTE1NmQyNjk5ODFmZGRiOGVmZDk4OWI4ZTY2YjFhYmY0NDcyOWY5ZDU2NjIzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.tDO06igdcYzE-Wir4CNR3g512cCtPLTOklWcbyI8Srk)
Sorry for the long description Could you please help me here
The text was updated successfully, but these errors were encountered: