meteor 1.5 eisdir error

[QHose]

with meteor 1.5 I get this error. also see nodejs/node#6861

/root/.meteor/packages/meteor-tool/.1.5.0.utbu0o++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:218     
      throw error;                                                                                                                                                                
      ^                                                                                                                                                                           
                                                                                                                                                                                  
Error: EISDIR: illegal operation on a directory, unlink '/opt/meteor/src/.meteor/local/dev_bundle'                                                                                
    at Error (native)                                                                                                                                                             
    at Object.fs.unlinkSync (fs.js:932:18)                                                                                                                                        
    at exports.makeLink (/tools/cli/dev-bundle-links.js:20:8)                                                                                                                     
    at [object Object]._.extend.ensureDevBundleLink (/tools/project-context.js:1476:7)                                                                                            
    at [object Object]._.extend._readFile (/tools/project-context.js:1410:10)                                                                                                     
    at new exports.ReleaseFile (/tools/project-context.js:1360:8)                                                                                                                 
    at /tools/cli/main.js:898:22                                                                                                                                                  

[QHose]

Note that i use Windows 10

[jshimko]

That looks like yet another issue with the Meteor build tool's filesystem handling.

Round 1
meteor/meteor#7852

My fix for that
meteor/meteor#8491

Reverted because of Windows bugs
meteor/meteor#8569

Which has now left it broken in new ways
reactioncommerce/reaction#2333

At this point, I've spent dozens of hours trying to fix Meteor's build tool issues when building inside Docker containers and I just don't even know what to do about it at this point. Unless the issue happens for them or gets pointed out by a lot of people, it doesn't get prioritized (like when my PR that fixed meteor/meteor#7852 got reverted and left us all hanging with breaking macOS builds again)

That error is absolutely not a problem from this image though. It's in the Meteor build tool's file handling methods. Unfortunately, I think I need to punt this one to them this time. Can you please file an issue over at the Meteor repo and share your details? I don't have a Windows machine so I can't file it, but I'd be happy to chime in if there's supporting info that I can provide. I really just want them to see that Docker builds are still broken after 7 months of this stuff. (builds consistently work on Linux machines, so that's what most people have been doing to work around it)

[jshimko]

Any update on this? I haven't heard of anyone else reporting this yet. Can you confirm the latest builds still don't work for you? If so, can you provide a repo to reproduce the issue?

[januszdorosz]

i have the same problem

/root/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser
      throw error;
      ^

Error: EISDIR: illegal operation on a directory, unlink '/opt/meteor/src/.meteor
    at Error (native)

[richardkeller411]

I have the same problem....

Windows 10 also tried to compose under Windows Subsystem for Linux with same error