v1.36.0 Docker Image Tries to Create /cache

[theory]

What version of Hugo are you using (hugo version)?

1.36.0

Does this issue reproduce with the latest release?

Yes.

Issue

The v1.36.0 Docker image appears to try to create the directory /cache/. See, for example, this Workflow run, which errors with:

Error: failed to load config: failed to create cache dir: mkdir /cache/: permission denied

This was not the case with v1.35.0. The only change in that workflow build is:

--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -8,8 +8,8 @@ jobs:
       - name: Check out Source
         uses: actions/checkout@v4
       - name: Build the Site
-        uses: docker://ghcr.io/gohugoio/hugo:v0.135.0
-        with: { entrypoint: hugo }
+        uses: docker://ghcr.io/gohugoio/hugo:v0.136.0
+        with: { args: build }
       - name: Generate Publish Script
         run: ./bin/publish public justatheory.com E1X44SJ45FTNGI 1 > publish.sh
       - name: Publish the Site

[bep]

Look at my "note" comment in the release notes. Documentation will follow, but if you follow some of the links in the release notes, there are some context.

[theory]

Hmmm…I see this line; I don't think I uses any caching, though. Happy to await doc updates.

[bep]

@theory everyone who uses Hugo use caching to some extent. I guess I forgot to link to PR #12921 in the release notes that had the most relevant info.

Example Docker run:

docker run --rm -v .:/project -v $HOME/Library/Caches/hugo_cache:/cache imagename build

We now expect a mount from the host to /cache in the container that we use as the value for HUGO_CACHEDIR.

We could (should?) possibly make this optional (or at least validate and throw a better error), but this is very important, especially for larger Hugo sites that do image processing; with the above you would have a Hugo cache that's not thrown away with the container.

[theory]

Ah-hah. I wonder if I should sue the caching action. My builds are always super fast, though.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.