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
$ git clone https://github.com/docker-library/official-images.git
Cloning into 'official-images'...
remote: Enumerating objects: 93744, done.
remote: Counting objects: 100% (228/228), done.
remote: Compressing objects: 100% (128/128), done.
remote: Total 93744 (delta 132), reused 183 (delta 100), pack-reused 93516
Receiving objects: 100% (93744/93744), 21.82 MiB | 15.65 MiB/s, done.
Resolving deltas: 100% (64747/64747), done.
error: invalid path '.external-pins/mcr.microsoft.com/windows/nanoserver:1809'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
The Windows file naming convention states that the following are reserved characters
< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)
So in this case, the issue is with the colon character. Is it possible to rename those files (nanoserver:1809, nanoserver:ltsc2022, servercore:1809, servercore:ltsc2022)?
The text was updated successfully, but these errors were encountered:
keeganwitt
changed the title
Clone and update fail on Windows
Git checkout fails on Windows
Nov 29, 2022
Doh, yep -- as noted in #13567 (comment), I tested this, but only with MSYS touch that comes with Git for Windows, so I (wrongly) assumed Git would make the same intelligent conversions automatically that MSYS does.
Cloning (or pulling) the repository now fails.
The Windows file naming convention states that the following are reserved characters
<
(less than)>
(greater than):
(colon)"
(double quote)/
(forward slash)\
(backslash)|
(vertical bar or pipe)?
(question mark)*
(asterisk)So in this case, the issue is with the colon character. Is it possible to rename those files (nanoserver:1809, nanoserver:ltsc2022, servercore:1809, servercore:ltsc2022)?
The text was updated successfully, but these errors were encountered: