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

Issues with running docker locally on Windows 10 #1540

Closed
sidtechnical opened this issue Jul 6, 2023 · 37 comments
Closed

Issues with running docker locally on Windows 10 #1540

sidtechnical opened this issue Jul 6, 2023 · 37 comments

Comments

@sidtechnical
Copy link

image

Unsure if this is an issue with my PC or something with the al-folio docker image.

@george-gca
Copy link
Collaborator

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.

@nicholaiTukanov
Copy link

I have the same issue +1

@nicholaiTukanov
Copy link

nicholaiTukanov commented Jul 11, 2023

This is the exact error I am getting:

al-folio-website  |          Rendering: _posts/2021-07-04-diagrams.md/#excerpt
al-folio-website  |   Pre-Render Hooks: _posts/2021-07-04-diagrams.md/#excerpt
al-folio-website  |   Rendering Liquid: _posts/2021-07-04-diagrams.md/#excerpt
al-folio-website  |   Liquid Exception: stack level too deep in /srv/jekyll/_posts/2021-07-04-diagrams.md/#excerpt
... <repeats for a while>
al-folio-website  |   Liquid Exception: stack level too deep in /srv/jekyll/_posts/2021-07-04-diagrams.md/#excerpt
al-folio-website  |   Liquid Exception: stack level too deep in /srv/jekyll/_posts/2021-07-04-diagrams.md

@george-gca here is my stack trace:

al-folio-website  | bundler: failed to load command: jekyll (/usr/local/bin/jekyll)
al-folio-website  | /var/lib/gems/3.1.0/gems/jekyll-4.3.2/lib/jekyll/frontmatter_defaults.rb:63:in `find': stack level too deep (SystemStackError)
al-folio-website  |     from /var/lib/gems/3.1.0/gems/jekyll-4.3.2/lib/jekyll/document.rb:58:in `block in initialize'
al-folio-website  |     from /var/lib/gems/3.1.0/gems/jekyll-4.3.2/lib/jekyll/drops/excerpt_drop.rb:19:in `name'
al-folio-website  |     from /var/lib/gems/3.1.0/gems/jekyll-4.3.2/lib/jekyll/drops/drop.rb:128:in `public_send'
al-folio-website  |     from /var/lib/gems/3.1.0/gems/jekyll-4.3.2/lib/jekyll/drops/drop.rb:128:in `[]'
al-folio-website  |     from /var/lib/gems/3.1.0/gems/jekyll-4.3.2/lib/jekyll/drops/drop.rb:205:in `block in to_h'
al-folio-website  |     from /var/lib/gems/3.1.0/gems/jekyll-4.3.2/lib/jekyll/drops/drop.rb:204:in `each'
al-folio-website  |     from /var/lib/gems/3.1.0/gems/jekyll-4.3.2/lib/jekyll/drops/drop.rb:204:in `each_with_object'
al-folio-website  |     from /var/lib/gems/3.1.0/gems/jekyll-4.3.2/lib/jekyll/drops/drop.rb:204:in `to_h'
al-folio-website  |      ... 9391 levels...
al-folio-website  |     from /var/lib/gems/3.1.0/gems/bundler-2.4.16/exe/bundler:4:in `load'
al-folio-website  |     from /var/lib/gems/3.1.0/gems/bundler-2.4.16/exe/bundler:4:in `<top (required)>'
al-folio-website  |     from /usr/local/bin/bundler:25:in `load'
al-folio-website  |     from /usr/local/bin/bundler:25:in `<main>'

Note: removing _posts/2021-07-04-diagrams.md creates a different issue:

al-folio-website  |   Liquid Exception: Liquid error (line 8): Cannot sort a null object. in _pages/projects.md

When I removed both _pages/projects.md and _posts/2021-07-04-diagrams.md, docker-compose up works for me on Windows 10.

@george-gca
Copy link
Collaborator

@nicholaiTukanov this happens with the code straight from the repo? Or did you change something already?

@nicholaiTukanov
Copy link

@george-gca yes this occurs straight from the repo

@george-gca
Copy link
Collaborator

No idea what that might be. Looking it up online, stack level too deep means that an infinite recursion might be occurring. The other error point to display_categories being null in projects.md.

This only happens on Windows with Docker and without changing a single line of code from the current main branch?

@pourmand1376
Copy link
Collaborator

pourmand1376 commented Jul 16, 2023

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.

@edwinfourriernicolai
Copy link

edwinfourriernicolai commented Sep 5, 2023

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 _posts/2021-07-04-diagrams.md seems enough in my case for docker-compose up to work on Windows 10.

@dannyboy990
Copy link

I had the same issue. removing _posts/2021-07-04-diagrams.md worked for me.

@fffmath
Copy link

fffmath commented Oct 8, 2023

I had the same issue. removing _posts/2021-07-04-diagrams.md worked for me.

Same to me.

@pourmand1376 pourmand1376 pinned this issue Oct 8, 2023
@george-gca
Copy link
Collaborator

@pourmand1376 is the mermaid dependency installed in the Dockerfile? Maybe this could be causing it. After I tackle #1609 maybe this issue changes?

@pourmand1376
Copy link
Collaborator

@george-gca
No. I don't think so. Shouldn't we include it in gemfile?

@george-gca
Copy link
Collaborator

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.

@pourmand1376
Copy link
Collaborator

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.

@george-gca
Copy link
Collaborator

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.

@gabrieldesouza02
Copy link

gabrieldesouza02 commented Oct 26, 2023

started with the same issue as you guys, removed _posts/2021-07-04-diagrams.md but that didn't help, removed _pages/projects.md and now I'm getting this error:

image

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:

image

is this a separate issue?

@george-gca
Copy link
Collaborator

Have your issue been solved @gabrieldesouza02?

@gabrieldesouza02
Copy link

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.

@george-gca
Copy link
Collaborator

It seems to be a problem with your pc accessing docker.io. Are you sure you can download docker images in this pc?

@gabrieldesouza02
Copy link

I have run docker images on this pc before , I don't think that's the issue

@gabrieldesouza02
Copy link

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

@pollostrazon
Copy link

Hi, I am having the same connection problem pointed out above. It happens both on Windows and WSL. Any tips?

@pourmand1376
Copy link
Collaborator

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 diagram file? If yes, please share your full log stacktrace.

@pollostrazon
Copy link

pollostrazon commented Dec 11, 2023

Hi, Have you deleted this diagram file? If yes, please share your full log stacktrace.

Hi. Yes, since that file is deleted it's able to run both docker compose pull and docker compose up. The problem is that I get "Cannot establish connection" through my browser (Firefox, but I tried Chrome and the situation is unchanged) when trying to run the site locally.

I am now trying to build it with docker compose up --build and see whether something changes.

@pollostrazon
Copy link

pollostrazon commented Dec 11, 2023

Update: the command
docker compose up --build
fails with
exec /tmp/entry_point.sh: no such file or directory
when trying to attach the container.

@pourmand1376
Copy link
Collaborator

Can you use this and output the stacktrace?

docker run -p 8080:8080 --name jekyll -v $(pwd):/srv/jekyll amirpourmand/al-folio:v0.10.0

@pollostrazon
Copy link

pollostrazon commented Dec 11, 2023

I couldn't include the -v option though cause it returns
docker: invalid reference format. See 'docker run --help'.
Here is the log without it

Resolving dependencies...
  Logging at level: debug
    Jekyll Version: 4.3.2
Configuration file: none
  Logging at level: debug
    Jekyll Version: 4.3.2
            Source: /srv/jekyll
       Destination: /srv/jekyll/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
       EntryFilter: excluded /.jekyll-cache
       EntryFilter: excluded /Gemfile.lock
       EntryFilter: excluded /Gemfile
        Generating: JekyllGetJson::GetJsonGenerator finished in 4.6161e-05 seconds.
No config
        Generating: Jekyll::Scholar::DetailsGenerator finished in 1.5146e-05 seconds.
        Generating: Jekyll::Archives::Archives finished in 9.2438e-05 seconds.
        Generating: JekyllJupyterNotebook::Generator finished in 8.7702e-05 seconds.
       Jekyll Feed: Generating feed for posts
        Generating: JekyllFeed::Generator finished in 0.001702735 seconds.
       Imagemagick: Disabled in site.config
        Generating: JekyllImagemagick::ImageGenerator finished in 2.3921e-05 seconds.
         AutoPages: Disabled/Not configured in site.config.
        Pagination: Disabled in site.config.
        Generating: Jekyll::PaginateV2::Generator::PaginationGenerator finished in 0.000267959 seconds.
        Generating: Jekyll::JekyllSitemap finished in 0.001565178 seconds.
         Rendering: feed.xml
  Pre-Render Hooks: feed.xml
  Rendering Liquid: feed.xml
  Rendering Markup: feed.xml
Post-Convert Hooks: feed.xml
  Rendering Layout: feed.xml
         Rendering: sitemap.xml
  Pre-Render Hooks: sitemap.xml
  Rendering Liquid: sitemap.xml
  Rendering Markup: sitemap.xml
Post-Convert Hooks: sitemap.xml
  Rendering Layout: sitemap.xml
         Rendering: robots.txt
  Pre-Render Hooks: robots.txt
  Rendering Liquid: robots.txt
  Rendering Markup: robots.txt
Post-Convert Hooks: robots.txt
  Rendering Layout: robots.txt
                    done in 0.024 seconds.
         Requiring: jekyll-watch
           Watcher: Ignoring (?-mix:^_site\/)
           Watcher: Ignoring (?-mix:^\.jekyll\-cache\/)
           Watcher: Ignoring (?-mix:^Gemfile)
           Watcher: Ignoring (?-mix:^Gemfile\.lock)
 Auto-regeneration: enabled for '/srv/jekyll'
LiveReload address: http://0.0.0.0:35729
[2023-12-11 09:43:42] INFO  WEBrick 1.8.1
[2023-12-11 09:43:42] INFO  ruby 3.1.2 (2022-04-12) [x86_64-linux-gnu]
[2023-12-11 09:43:42] DEBUG WEBrick::HTTPServlet::FileHandler is mounted on /.
[2023-12-11 09:43:42] DEBUG unmount .
[2023-12-11 09:43:42] DEBUG Jekyll::Commands::Serve::Servlet is mounted on .
    Server address: http://0.0.0.0:8080
[2023-12-11 09:43:42] INFO  WEBrick::HTTPServer#start: pid=1 port=8080
  Server running... press ctrl-c to stop.

@pourmand1376
Copy link
Collaborator

Good. Now go to localhost:8080 and it should be fine.

@pollostrazon
Copy link

Good. Now go to localhost:8080 and it should be fine.

image
It just shows me the list of files in the webpage, but no preview of it. Also, it seems there is no content except from these .XML files.

@pollostrazon
Copy link

Update: I had to rerun docker compose up for some reasons and stuff showed up! Ty so much!

This does not resolve the marmaid problem though...

@george-gca
Copy link
Collaborator

@pollostrazon check if the mermaid problem is solved now.

@pourmand1376
Copy link
Collaborator

pourmand1376 commented Jan 3, 2024

@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.

@pollostrazon
Copy link

I re-cloned the default repository in a new folder and re-pulled everything. docker compose up now works fine!
The issue is now solved for me!

@george-gca
Copy link
Collaborator

Should we close this issue?

@pollostrazon
Copy link

Should we close this issue?

I think so. Now everything seems to be up and running. Ty!

@pourmand1376
Copy link
Collaborator

I think we should unpin this issue if it is silent in two weeks.

@george-gca
Copy link
Collaborator

The problem is some people open new issues that maybe the cause is this one here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants