# Zola failing opaquely after 0.22.0 upgrade

**URL:** <https://zola.discourse.group/t/zola-failing-opaquely-after-0-22-0-upgrade/2895>\
**Category:** Uncategorized\
**Created:** [January 15, 2026, 11:59am UTC](https://zola.discourse.group/t/zola-failing-opaquely-after-0-22-0-upgrade/2895 "2026-01-15T11:59:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![brianhicks](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/brianhicks/32/384_2.png) [@brianhicks](https://zola.discourse.group/u/brianhicks)\
**Post date:** [January 15, 2026, 11:59am UTC](https://zola.discourse.group/t/zola-failing-opaquely-after-0-22-0-upgrade/2895/1 "2026-01-15T11:59:11Z")

</div>

Hello! I recently upgraded to Zola 0.22.0, and after figuring out all the new syntax highlighting stuff I can get a local build. Great! But then, when I try to build in GHA or Docker, I get this:

```auto
Building site...
ERROR Failed to build the site
ERROR I/O error: No such file or directory (os error 2)
ERROR Reason: No such file or directory (os error 2)

```

I haven’t had any luck figuring out what could be going on there. For whatever reason, setting `RUST_LOG=trace` doesn’t have any effect the way it does locally (macOS.) How can I get Zola to tell me what it’s trying to open and failing?

If you want to see the code for this site, it’s all available at [zola fixes by BrianHicks · Pull Request #74 · bytes-zone/bytes-zone · GitHub](https://github.com/bytes-zone/bytes-zone/pull/74)

---

<div class="post-metadata">

**Author:** ![thomasweitzel](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/thomasweitzel/32/1011_2.png) [@thomasweitzel](https://zola.discourse.group/u/thomasweitzel)\
**Post date:** [January 15, 2026, 2:24pm UTC](https://zola.discourse.group/t/zola-failing-opaquely-after-0-22-0-upgrade/2895/2 "2026-01-15T14:24:09Z")

</div>

Hi Brian,

the problem is a lowercase “l” in your additional grammar file name in `config.toml`: it should be `syntaxes/alloy.tmLanguage.json` and not `syntaxes/alloy.tmlanguage.json` (“language” should be capitalized).

I don’t know how to convince Zola to provide more helpful output, but my process disables all optional refernces to files in `config.toml` and then re-enable one after the other, until I hit the error.

Yes, the error message could be more helpful 😉

BTW: nice looking theme!

---

<div class="post-metadata">

**Author:** ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)\
**Post date:** [January 16, 2026, 9:25am UTC](https://zola.discourse.group/t/zola-failing-opaquely-after-0-22-0-upgrade/2895/3 "2026-01-16T09:25:40Z")

</div>

Oh that’s weird that the path is not mentioned, we should really move to use fs-err everywhere. In practice yeah if it works on macOS but not linux it’s _probably_ case sensitivity related as @thomasweitzel said.

I’ve made [Use fs-err everywhere · Issue #3082 · getzola/zola · GitHub](https://github.com/getzola/zola/issues/3082) to track it

---

<div class="post-metadata">

**Author:** ![brianhicks](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/brianhicks/32/384_2.png) [@brianhicks](https://zola.discourse.group/u/brianhicks)\
**Post date:** [January 16, 2026, 12:22pm UTC](https://zola.discourse.group/t/zola-failing-opaquely-after-0-22-0-upgrade/2895/4 "2026-01-16T12:22:41Z")

</div>

yep, apfs strikes again. Thank you both!