Jekyll::Converters::Scss: end of file reached while setting up website via Docker

[rishabh2002chauhan]

Following error is shown when website is build via docker with docker run --rm --volume="%CD%:/srv/jekyll" -it jekyll/jekyll:stable ./build.sh command in command prompt in windows.
System OS: windows 11

Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/releases/4.3.noscript.scss':
                    end of file reached
                    ------------------------------------------------
      Jekyll 4.4.1   Please append `--trace` to the `build` command
                     for any additional information or backtrace.
                    ------------------------------------------------

[zuedev]

Can confirm this is happening with a fresh clone of the repo at 1ad646b.

@rishabh2002chauhan try running this instead: (in powershell!)

docker run --rm -v "${PWD}:/srv/jekyll" -w /srv/jekyll -p 4000:4000 -e SERVER_HOST=0.0.0.0 -it ruby:3.2 bash -c "apt-get update && apt-get install -y build-essential libffi-dev libmagic-dev && curl -fsSL https://github.com/tdewolff/minify/releases/latest/download/minify_linux_amd64.tar.gz | tar -xz -C /usr/local/bin minify && ./build-and-serve.sh"

I believe the root cause is that the jekyll/jekyll:stable Docker image runs on Alpine Linux, which uses musl libc. The sass-embedded gem bundles a pre-compiled Dart Sass binary that's built for glibc, so it just crashes on launch. The end of file reached (EOFError) error is a bit misleading — it's actually Ruby trying to read from Dart Sass's stdout, but the process is already dead because the binary can't run on musl.

Downgrading to sassc/LibSass (jekyll-sass-converter 2.x) doesn't help either, since the project's SCSS uses modern Dart Sass module syntax (@use, namespaced variables like colors.$godot-blue) that LibSass doesn't support at all.

The fix would be to switch the Docker setup to a glibc-based image (e.g. ruby:3.2-slim on Debian) instead of Alpine, so the Dart Sass binary can actually run.

P.S. Since this means setting up a custom Dockerfile anyway, it might be a good opportunity to properly containerize the jekyll site for both dev and prod as we'd already be doing most of the work for that as part of this fix. Thoughts?

[rishabh2002chauhan]

@zuedev , the command is working fine but I have one more issue.
whenever I am doing any changes, for e.g. in _i18n/en.yml, they are not getting reflected back on the served site. Any idea why?

[zuedev]

@rishabh2002chauhan You got two choices:

1. After changing a data/i18n file, trivially edit the page that uses it, or just restart the server.
2. Set incremental: false in _config.development.yml! *

* Jekyll's incremental build only regenerates files that have changed themselves. It does not regenerate pages that depend on changed data files like _i18n/en.yml. So when you edit a translation file or data file, the pages that consume that data are not rebuilt.

[rishabh2002chauhan]

@zuedev I tried both the options but there is still no immediate change seen after refresh. I thought it might be a docker issue but 'force-polling' is already set to true for that.
I just found that its taking almost 5 -10 mins to reflect the changes whether I change the '_config.development.yml' file or not. Even restarting the server is not reflecting changes until 5-10 mins have passed.

Is there any other command I can use for restarting the server besides

docker run --rm -v "${PWD}:/srv/jekyll" -w /srv/jekyll -p 4000:4000 -e SERVER_HOST=0.0.0.0 -it ruby:3.2 bash -c "apt-get update && apt-get install -y build-essential libffi-dev libmagic-dev && curl -fsSL https://github.com/tdewolff/minify/releases/latest/download/minify_linux_amd64.tar.gz | tar -xz -C /usr/local/bin minify && ./build-and-serve.sh"

?