Skip to content

Git submodule update fails with error 66 in docker/windows #1661

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

Closed
1 task
derekwbrown opened this issue May 4, 2018 · 8 comments
Closed
1 task

Git submodule update fails with error 66 in docker/windows #1661

derekwbrown opened this issue May 4, 2018 · 8 comments

Comments

@derekwbrown
Copy link

  • I was not able to find an open or closed issue matching what I'm seeing

This is the exact issue referenced #1303
I have attempted the solution(s) suggested in the above issue, to no avail

Setup

Git for Windows x64; tried several versions (as referenced in the issue above)

$ git --version --build-options

git --version --build-options
git version 2.14.1.windows.1
built from commit: 82d9b3f3b2407b52251620597d4b14933685459d
sizeof-long: 4
machine: x86_64

Have also tried the referenced busybox version, and 2.17.1

Host is Windows 10 pro 10.0.16299.371
Container is microsoft/windowsservercore
reports 10.0.14393

$ cmd.exe /c ver

** insert your machine's response here **


 - What options did you set as part of the installation? Or did you choose the
   defaults?

One of the following:

type "C:\Program Files\Git\etc\install-options.txt"
type "C:\Program Files (x86)\Git\etc\install-options.txt"
type "%USERPROFILE%\AppData\Local\Programs\Git\etc\install-options.txt"
$ cat /etc/install-options.txt

**type install-options.txt
Path Option: Cmd
SSH Option: OpenSSH
CURL Option: OpenSSL
CRLF Option: CRLFAlways
Bash Terminal Option: MinTTY
Performance Tweaks FSCache: Enabled
Use Credential Manager: Enabled
Enable Symlinks: Disabled

Details

  • Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other

cmd (within docker container)

git submodule update --init --recursive
  • What did you expect to occur after running these commands?

success

  • What actually happened instead?

failure, error code 66

@dscho
Copy link
Member

dscho commented May 5, 2018

This seems related (including the follow-up comments suggesting that current snapshot builds may have fixed this bug): #1007 (comment)

@rbodziony
Copy link

@dscho
Copy link
Member

dscho commented May 21, 2018

@derekwbrown would you please give your feedback as to the suggestion that this is addressed by switching to BusyBox-based MinGit? This is supposed to be a conversation here, not a golden record on Voyager sent to the aliens.

@rbodziony
Copy link

checked and this version (from above) works in winsdowsservercore containers but not in nano

@derekwbrown
Copy link
Author

@dscho version above (2.17.0.1.53 busybox) appears to work. Sorry for the slow response; I have other things occupying my time besides this.

@dscho
Copy link
Member

dscho commented Aug 16, 2018

Sorry for the slow response;

@derekwbrown that's fine; I'll just adjust my response rate.

@dscho
Copy link
Member

dscho commented Jan 1, 2020

As much as I would love to assist any interested developer in fixing this, that would first need such an interested developer: I cannot justify working on this issue myself, the target audience is much too small.

@dscho
Copy link
Member

dscho commented Oct 15, 2021

Closing this as stale.

@dscho dscho closed this as completed Oct 15, 2021
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

3 participants