Issues with running docker locally on Windows 10 #1540

sidtechnical · 2023-07-06T16:30:00Z

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

george-gca · 2023-07-08T16:59:49Z

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 · 2023-07-11T22:13:32Z

I have the same issue +1

nicholaiTukanov · 2023-07-11T22:14:06Z

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 · 2023-07-12T01:48:33Z

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

nicholaiTukanov · 2023-07-12T02:29:33Z

@george-gca yes this occurs straight from the repo

george-gca · 2023-07-12T13:41:15Z

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 · 2023-07-16T05:03:15Z

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 · 2023-09-05T11:10:01Z

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 · 2023-09-11T11:33:54Z

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

fffmath · 2023-10-08T14:18:03Z

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

Same to me.

george-gca · 2023-10-11T23:16:30Z

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

pourmand1376 · 2023-10-12T18:51:55Z

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

george-gca · 2023-10-13T22:30:50Z

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 · 2023-10-21T16:52:26Z

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 · 2023-10-21T19:32:13Z

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 · 2023-10-26T02:56:59Z

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:

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?

george-gca · 2023-11-22T19:50:48Z

Have your issue been solved @gabrieldesouza02?

gabrieldesouza02 · 2023-11-22T20:48:06Z

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 · 2023-11-23T14:42:25Z

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

gabrieldesouza02 · 2023-11-25T19:18:38Z

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

gabrieldesouza02 · 2023-11-25T19:19:53Z

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 · 2023-12-11T08:49:08Z

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

pourmand1376 · 2023-12-11T08:58:10Z

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 · 2023-12-11T09:04:37Z

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 · 2023-12-11T09:08:56Z

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 · 2023-12-11T09:15:22Z

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 · 2023-12-11T09:46:10Z

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 · 2023-12-11T10:05:18Z

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

pollostrazon · 2023-12-11T10:08:12Z

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

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 · 2023-12-11T10:10:55Z

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 · 2024-01-03T01:46:49Z

@pollostrazon check if the mermaid problem is solved now.

pourmand1376 · 2024-01-03T05:33:55Z

@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 · 2024-01-03T10:31:21Z

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 · 2024-01-03T16:31:20Z

Should we close this issue?

pollostrazon · 2024-01-03T17:48:31Z

Should we close this issue?

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

pourmand1376 · 2024-01-19T07:35:55Z

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

george-gca · 2024-01-19T13:54:09Z

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

pourmand1376 added docker bug labels Jul 11, 2023

pourmand1376 pinned this issue Oct 8, 2023

george-gca closed this as completed Jan 3, 2024

Issues with running docker locally on Windows 10 #1540

Issues with running docker locally on Windows 10 #1540

Comments

sidtechnical commented Jul 6, 2023

george-gca commented Jul 8, 2023

nicholaiTukanov commented Jul 11, 2023

nicholaiTukanov commented Jul 11, 2023 • edited

george-gca commented Jul 12, 2023

nicholaiTukanov commented Jul 12, 2023

george-gca commented Jul 12, 2023

pourmand1376 commented Jul 16, 2023 • edited

edwinfourriernicolai commented Sep 5, 2023 • edited

dannyboy990 commented Sep 11, 2023

fffmath commented Oct 8, 2023

george-gca commented Oct 11, 2023

pourmand1376 commented Oct 12, 2023

george-gca commented Oct 13, 2023

pourmand1376 commented Oct 21, 2023

george-gca commented Oct 21, 2023

gabrieldesouza02 commented Oct 26, 2023 • edited

george-gca commented Nov 22, 2023

gabrieldesouza02 commented Nov 22, 2023

george-gca commented Nov 23, 2023

gabrieldesouza02 commented Nov 25, 2023

gabrieldesouza02 commented Nov 25, 2023

pollostrazon commented Dec 11, 2023

pourmand1376 commented Dec 11, 2023

pollostrazon commented Dec 11, 2023 • edited

pollostrazon commented Dec 11, 2023 • edited

pourmand1376 commented Dec 11, 2023

pollostrazon commented Dec 11, 2023 • edited

pourmand1376 commented Dec 11, 2023

pollostrazon commented Dec 11, 2023

pollostrazon commented Dec 11, 2023

george-gca commented Jan 3, 2024

pourmand1376 commented Jan 3, 2024 • edited

pollostrazon commented Jan 3, 2024

george-gca commented Jan 3, 2024

pollostrazon commented Jan 3, 2024

pourmand1376 commented Jan 19, 2024

george-gca commented Jan 19, 2024

nicholaiTukanov commented Jul 11, 2023 •

edited

pourmand1376 commented Jul 16, 2023 •

edited

edwinfourriernicolai commented Sep 5, 2023 •

edited

gabrieldesouza02 commented Oct 26, 2023 •

edited

pollostrazon commented Dec 11, 2023 •

edited

pollostrazon commented Dec 11, 2023 •

edited

pollostrazon commented Dec 11, 2023 •

edited

pourmand1376 commented Jan 3, 2024 •

edited