Error: EISDIR: illegal operation on a directory error while generating project in Docker #5180
-
I have a long running project in Error: EISDIR: illegal operation on a directory, open '' My
I run the build locally with
I ended up with Even when I used The only workaround I found is to generate the project locally (on my local computer), store in GitLab and then push it to server (I am using Am I missing something? Is there anything I should do / try to fix the issue? 🙏 Note: I also asked this question on SO - https://stackoverflow.com/questions/75904647/error-eisdir-illegal-operation-on-a-directory-error-while-generating-project-i |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 3 replies
-
Questions
|
Beta Was this translation helpful? Give feedback.
-
Every directory from my project. Please note, that I removed the problematic folder, and that the issue appeared for other folders.
Tested with
|
Beta Was this translation helpful? Give feedback.
-
See also #4682 |
Beta Was this translation helpful? Give feedback.
-
@yoshinorin I checked the related issue #4682 and and I changed Now it runs differently. What it does - it generates much less files (101 instead of 150 in the working version) where each blog post becomes a file with HTML contents instead of directory with Before (correct, original, Hexo 3, Node 12):
After (Hexo 6, Node 18, post_asset_folder: false)
No errors in logs. |
Beta Was this translation helpful? Give feedback.
-
After digging more into related issue, I believe I found and implemented the workaround.
Before:
After:
Once this was done, all started to work like a charm. This comment I initially ignored, but then I investigated it further: #4682 (comment) This could be potentially added to the official troubleshooting page. |
Beta Was this translation helpful? Give feedback.
@yoshinorin @stevenjoezhang
After digging more into related issue, I believe I found and implemented the workaround.
post_asset_folder
(true
)permalink
property for each blog post and I appended/
to it:Before:
After:
Once this was done, all started to work like a charm.
This comment I initially ignored, but then I investigated it further: #4682 (comment)
This could be potentially added to the official troubleshooting page.