Just had a strange error when renbuilding one of the websites I’m in charge of.. Pretty quickly it turned out, that Jekyll was broken..!? Ruby itself was running as usual, but I couldn’t even ask Jekyll for its version.

The error was very cryptic and didn’t provide any hint on how to fix things. The internet also didn’t help much, that’s why I’m logging it here. I just managed to fix it by chance: A (rather unsimilar) bug report was talking about sassc. As I did not have an idea on how to approach the problem, I just tried (re)installing the tool. And it did the trick…!? Not sure why, and not sure why it wasn’t installed as a dependency with Jekyll, or …!?

However, running

did fixed it for me (patch for the corresponding Docker image).

## Update

The above didn’t actually fully-solve the problem. It just re-installed sassc locally, which fixed the issue in the container on the current platform. However, when I compile the very same image at the Docker Hub and pull the new version it’s broken again..!? The sassc compilation product seems to be plattform dependent!? #wtf

Anyway. I finally got it fixed by installing sassc using --disable-march-tune-native, see also github.com/sass/sassc-ruby/issues/146:

The updated patch for my Docker image is available from GitHub.

## Log

Maybe that can be of help for somebody else? Here is the full error that was thrown: