node nano dockerfile failed with error "The filename or extension is too long"
See original GitHub issueI tried the node nano dockerfile,
FROM nanoserver
COPY nodejs /windows/system32
CMD [ "node.exe" ]
with hyper-v container nano image, it works pretty well. But when I tried it in a windows TP5 nano server (in Azure), it failed with below error:
msg="hcsshim::ImportLayer failed in Win32: The filename or extension is too long. (0xce) layerId=\\\\?\\C:\\ProgramData\\docker\\windowsfilter\\0cca83375d700cfdc9dfb627b4102584a767720ba4cf55339f63020fc2aa7deb flavour=1 folder=C:\\Windows\\TEMP\\hcs306829939"
Have you tried it in nano server? Is there any difference between nano server container and hyper-v nano container?
Any help will be highly appreciated. Thanks.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Update Error "The filename or extension is too long" #29
Trying to upgrade from nodejs: 8.9.1-0 conda-forge --> 9.9.0-0 conda-forge Receive the following error: Downloading and Extracting Packages ...
Read more >Adding imagemagick into my php 7.4 docker raised error
The message. You should add "extension=imagick.so" to php.ini. is just a warning that is addressed later in your Dockerfile. The real error ......
Read more >Store configuration data using Docker Configs
When a container task stops running, the configs shared to it are unmounted from the in-memory filesystem for that container and flushed from...
Read more >9 Common Dockerfile Mistakes - Runnablog - Runnable
In this article, we'll talk about what mistakes people commonly make, and how to write them better. For those of you who are...
Read more >How to Debug a Node.js app in a Docker Container
In this post, I'm going to teach how you can debug a Node.js app in a Docker container ... half of Node.js users...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This long path issue has been fixed in RTM build. Thanks:)
That is a good idea! I am using this instruction: https://github.com/mongodb/mongo/wiki/Build-Mongodb-From-Source#windows-specific-instructions.
But the build cost about 1.5 hours in my dev machine (Core i7-3770, 16GB) using 1 parallel job, it may be a pain for container.