Skip to content
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

wclayer import does not work properly with long path #285

Closed
liangyuRain opened this issue Aug 14, 2018 · 2 comments
Closed

wclayer import does not work properly with long path #285

liangyuRain opened this issue Aug 14, 2018 · 2 comments

Comments

@liangyuRain
Copy link

I was using wclayer to import layers. It seems that if the target directory has a long path, wclayer does not work properly.

I was importing the base layer from microsoft/nanoserver. The layer can be downloaded from https://az896309.vo.msecnd.net/containers/microsoft/nanoserver:10.0.14393.447_en-us_full_spx2q06478MkUJl5hOPmCKDgYiXoSLt3. When I imported it with

.\wclayer.exe import -i .\nanoserver_10.0.14393.447_en-us_full_spx2q06478MkUJl5hOPmCKDgYiXoSLt3 C:\temp_short

the extracted folder has 1.13 GB. However, if I imported it with

.\wclayer.exe import -i .\nanoserver_10.0.14393.447_en-us_full_spx2q06478MkUJl5hOPmCKDgYiXoSLt3 C:\temp_long\abcdef\ghijklmn\opqrst\uvwxyz\abcd\efghijk\lmnopq\rst\uvwxyz\abcdefghijklmn\opqrstuvwxyz

the extracted folder has only 81.3 MB.

I have also tried to add long path prefix:

.\wclayer.exe import -i .\nanoserver_10.0.14393.447_en-us_full_spx2q06478MkUJl5hOPmCKDgYiXoSLt3 \\?\C:\temp_long\abcdef\ghijklmn\opqrst\uvwxyz\abcd\efghijk\lmnopq\rst\uvwxyz\abcdefghijklmn\opqrstuvwxyz

wclayer failed with mkdir \\?: The filename, directory name, or volume label syntax is incorrect., so I created the directory first and ran the command again. The extracted folder also has only 81.3 MB. Therefore, I suspect that if the target path is too long, some files get ignored during the import.

@liangyuRain
Copy link
Author

Sorry, this is probably the problem of Windows explorer. The Windows explorer does not support long path, so the size becomes different.

@lowenna
Copy link
Contributor

lowenna commented Aug 24, 2018

@liangyuRain So this can be closed, right?

dcantah pushed a commit to dcantah/hcsshim that referenced this issue Mar 17, 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

2 participants