-
Notifications
You must be signed in to change notification settings - Fork 419
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
update to 3.6.4 breaks git sync #696
Comments
This looks like a fairly recent change in git. I will have to figure out
what tickles this and add a test case.
…On Mon, Mar 13, 2023, 4:41 PM vsubram95 ***@***.***> wrote:
git-sync v3.6.4 breaks the cloning process in our k8s pods with the issue
mentioned. However, it works fine until version v3.6.3 .
Note:
1. We use *submodules* in our repos.
2. This is *git-sync* deployed as sidecar container in airflow via helm
`E0313 04:24:55.774672 12 main.go:535] "msg"="too many failures, aborting"
"error"="Run(git rev-parse HEAD): exit status 128: { stdout: "", stderr:
"fatal: detected dubious ownership in repository at '/dags'
To add an exception for this directory, call:
\tgit config --global --add safe.directory /dags" }" "failCount"=1`
—
Reply to this email directly, view it on GitHub
<#696>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKWAVC4GACZXHV7U3JZQ43W36WDNANCNFSM6AAAAAAVZXKEZ4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Ok, well the fix is pretty easy. I will try to prep a PR this week. |
@thockin , i am using v3.6.5 tag of git-sync container and i am getting the error is this problem related to the issue mentioned above ? |
Can you show me:
1) Full logs with `-v 6`
2) Your full commandline and env vars (you can XXX the repo and stuff)
…On Mon, Mar 20, 2023 at 6:52 AM vineet ***@***.***> wrote:
@thockin <https://github.com/thockin> , i am using v3.6.5 tag of git-sync
container and i am getting the error
"msg"="error syncing repo, will retry" "error"="Run(git sparse-checkout
init): exit status 128: { stdout: "", stderr: "fatal: detected dubious
ownership in repository at '/tmp'\nTo add an exception for this directory,
call:\n\n\tgit config --global --add safe.directory /tmp" }" "failCount"=25
"waitTime"=60000000000
is this problem related to the issue mentioned above ?
—
Reply to this email directly, view it on GitHub
<#696 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKWAVBSCHHZG7VOK4MWCMTW5BOKFANCNFSM6AAAAAAVZXKEZ4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
here are the logs for the git-sync sidecar container: I0321 06:40:40.730611 13 main.go:539] "level"=1 "msg"="syncing repo" and the args for the sync container are:
|
I think there are some logs missing from that listing? I ran this myself using 3.6.5 and I see:
The relevant parts are:
We added a safe.directory for you, but because you pointed the root at /tmp, which happens to be the default $HOME, the .gitconfig file gets blown away by the sync logic (git can't clone into a non-empty directory). This might have worked before because the config options in that file were not CRITICAL to your operation. But now they are. I could add logic to store the gitconfig somewhere else, but I would need to make a different $HOME, because I need a place to write the config that isn't /tmp. I think the better option is for you to use a different If you set |
yes, changing the --root to /tmp/git resolved the problem with git-sync. |
git-sync v3.6.4 breaks the cloning process in our k8s pods with the issue mentioned. However, it works fine until version v3.6.3 .
Note:
The text was updated successfully, but these errors were encountered: