You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a private repository which has many submodules, which are in our corporate git servers. We have self hosted runners which do the checkout. Every time when one of those submodules need to be updated (new commits), pull fails with Host key verification failed. ~/.ssh/known_hosts file must be correct, because when I run git submodule update locally on the same runner, there are no issues. It seems like known_hosts is not even read or something else is wrong. Here is the checkout action:
We have also many submodules which are in github.com, with which we have never trouble. Only with the ones which are outside of Github and have url ssh://server...
Could it be that checkout action does not respect user's known_hosts file since modifying it seems to have absolutely no effect?
The text was updated successfully, but these errors were encountered:
We have put a workaround until this issue is resolved:
First we disabled submodules from actions/checkout.
After the checkout, we run a step which updates the submodules:
...
run: |
git submodule sync --recursive
git submodule update --init --recursive --force
git submodule foreach --recursive
We have a private repository which has many submodules, which are in our corporate git servers. We have self hosted runners which do the checkout. Every time when one of those submodules need to be updated (new commits), pull fails with Host key verification failed. ~/.ssh/known_hosts file must be correct, because when I run git submodule update locally on the same runner, there are no issues. It seems like known_hosts is not even read or something else is wrong. Here is the checkout action:
We have also many submodules which are in github.com, with which we have never trouble. Only with the ones which are outside of Github and have url ssh://server...
Could it be that checkout action does not respect user's known_hosts file since modifying it seems to have absolutely no effect?
The text was updated successfully, but these errors were encountered: