The following NEW packages will be installed:Ġ upgraded, 1 newly installed, 0 to remove and 36 not upgraded.Īfter this operation, 11.3 MB of additional disk space will be used. The repository is setup! You can now install packages. Installing debian-archive-keyring which is needed for installingĪpt-transport-https on many Debian systems. + curl -s https: //packagecloud.io/install/repositories/github/git-lfs/ What is the output of git -version on your kubernetes instances? Is the git new enough to support LFS?Īdded a comment - 10:58 - edited I don't understand which work around you believe would resolve your issue in your kubernetes container. Can you confirm that git lfs install reports that git lfs is installed?Ĭan you perform the git init git remote add origin your_url git fetch origin git lfs fetch origin origin/master command from a shell step immediately prior to your checkout step?
That is quite odd, since I assume the preceding git lfs install is not reporting any errors. The message from the checkout step hints (to me) that the lfs command was not installed in a portion of the PATH defined for the checkout step. I would expect case insensitive file name extensions to cause that to break no matter what you did, since the typical Linux file system is case sensitive. That issue also mentions case insensitive file name extensions, yet you said that the clone works when you perform a git clone from inside the kubernetes pod. Your pod does not seem to be defining a credentials helper, so I assume it is not a credential helper issue.
That issue on GitHub seems to mention credential helpers, even though Linux machines (and kubernetes pods) rarely use credentials helpers. I don't understand which work around you believe would resolve your issue in your kubernetes container.
0 kommentar(er)
