-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
Issues with running docker locally on Windows 10 #1540
Comments
Please post the whole stacktrace here, as not only the pasted part doesn't give much info, but also the contrast of the error message is terrible. |
I have the same issue +1 |
This is the exact error I am getting:
@george-gca here is my stack trace:
Note: removing
When I removed both |
@nicholaiTukanov this happens with the code straight from the repo? Or did you change something already? |
@george-gca yes this occurs straight from the repo |
No idea what that might be. Looking it up online, This only happens on Windows with Docker and without changing a single line of code from the current main branch? |
I have seen this issue on windows. I know that removing those files fixes the problem. It is also odd that it only happens on windows. Maybe something to do with docker itself. Let's keep this open to see what other say. |
I have the same issue. I have tried with Windows 10 and Linux with Docker and without changing a single line of code from the current main branch. The issue occurs only with Windows. Removing only |
I had the same issue. removing _posts/2021-07-04-diagrams.md worked for me. |
Same to me. |
@pourmand1376 is the mermaid dependency installed in the Dockerfile? Maybe this could be causing it. After I tackle #1609 maybe this issue changes? |
@george-gca |
I would say it was not necessary since the blog post about it works, but I just realized that we actually include it in the deploy action, but not in the Dockerfile, so yes, I believe we should. |
I added that in gemfile, but the problem was not solved. |
I believe only adding in the Gemfile doesn't solve this. You should also add the npm line that we use in the deploy action. |
started with the same issue as you guys, removed that being said I have made some local changes though, my site is currently deployed and most of the changes are just on the landing page, if anybody thinks I may have changed something relevant I can look into what all my changes are exactly I also keep getting this when I try to access the page on my browser: is this a separate issue? |
Have your issue been solved @gabrieldesouza02? |
no it hasn't sadly. I was thinking of cloning the repo again and start from scratch. I haven't made too many changes anyways. |
It seems to be a problem with your pc accessing |
I have run docker images on this pc before , I don't think that's the issue |
I actually haven't been touching project recently though, whenever I get back to it I'll probably try cloning the repo and starting from scratch |
Hi, I am having the same connection problem pointed out above. It happens both on Windows and WSL. Any tips? |
Hi, Have you deleted this |
Hi. Yes, since that file is deleted it's able to run both I am now trying to build it with |
Update: the command |
Can you use this and output the stacktrace?
|
I couldn't include the -v option though cause it returns
|
Good. Now go to |
Update: I had to rerun This does not resolve the marmaid problem though... |
@pollostrazon check if the mermaid problem is solved now. |
It seems that mermaid is removed from dependencies. However, to see if the problem is solved, he needs to make sure that he removes the previous docker image and pull a new one. |
I re-cloned the default repository in a new folder and re-pulled everything. |
Should we close this issue? |
I think so. Now everything seems to be up and running. Ty! |
I think we should unpin this issue if it is silent in two weeks. |
The problem is some people open new issues that maybe the cause is this one here. |
Unsure if this is an issue with my PC or something with the al-folio docker image.
The text was updated successfully, but these errors were encountered: