Hugo Build Failed when using Ubuntu Noble 24.04 build image

Support
,
1

sitename: andremoreno
deployID: 677cc6c158438d00084a0eb7

Build Log:
1:17:12 PM: WARN Module “github/gohugoio/hugo-mod-bootstrap-scss/v5” is not compatible with this Hugo version: extended; run “hugo mod graph” for more information.
1:17:12 PM: Start building sites …
1:17:12 PM: hugo v0.140.2-aae02ca612a02e085c08366a9c9279f4abb39d94 linux/amd64 BuildDate=2024-12-30T15:01:53Z VendorInfo=gohugoio
1:17:34 PM: ERROR TOCSS: failed to transform “/scss/stylesheet.scss” (text/x-scss). Check your Hugo installation; you need the extended version to build SCSS/SASS with transpiler set to ‘libsass’.: this feature is not available in your current Hugo version, see for more information
1:18:26 PM: ERROR render of “/opt/build/repo/content/stories/_index.md” failed: “/opt/build/repo/layouts/stories/list.html:31:18”: execute of template failed: template: stories/list.html:31:18: executing “main” at <.Fill>: error calling Fill: this feature is not available in your current Hugo version, see for more information
1:18:26 PM: ERROR render of “/tags/anniversary” failed: “/opt/build/repo/layouts/tags/term.html:28:18”: execute of template failed: template: tags/term.html:28:18: executing “main” at <.Fill>: error calling Fill: this feature is not available in your current Hugo version, see for more information
1:18:26 PM: ERROR render of “/tags/baptism” failed: “/opt/build/repo/layouts/tags/term.html:28:18”: execute of template failed: template: tags/term.html:28:18: executing “main” at <.Fill>: error calling Fill: this feature is not available in your current Hugo version, see for more information
1:18:26 PM: Total in 79477 ms
1:18:26 PM: Error: error building site: TOCSS: failed to transform “/scss/stylesheet.scss” (text/x-scss). Check your Hugo installation; you need the extended version to build SCSS/SASS with transpiler set to ‘libsass’.: this feature is not available in your current Hugo version, see for more information
1:18:26 PM: ​
1:18:26 PM: “build.command” failed
1:18:26 PM: ────────────────────────────────────────────────────────────────
1:18:26 PM: ​
1:18:26 PM: Error message
1:18:26 PM: Command failed with exit code 1: hugo --gc --minify (Search results for '"non-zero exit code: 1"' - Netlify Support Forums)
1:18:26 PM: ​
1:18:26 PM: Error location
1:18:26 PM: In build.command from netlify.toml:
1:18:26 PM: hugo --gc --minify
1:18:26 PM: ​
1:18:26 PM: Resolved config
1:18:26 PM: build:
1:18:26 PM: command: hugo --gc --minify
1:18:26 PM: commandOrigin: config
1:18:26 PM: environment:
1:18:26 PM: - HUGO_VERSION
1:18:26 PM: - HUGO_ENABLEGITINFO
1:18:26 PM: - HUGO_ENV
1:18:26 PM: publish: /opt/build/repo/public
1:18:26 PM: publishOrigin: config
1:18:26 PM: headers:
1:18:27 PM: Failed during stage ‘building site’: Build script returned non-zero exit code: 2 (Search results for '"non-zero exit code: 2"' - Netlify Support Forums)

there is no build problems when using Ubuntu Focal 20.04 (default). So right now I’m still using this build image.

It seems that on Noble, the hugo installed is not the extended version.

when on Ubuntu Focal it showing like this:
1:19:29 PM: hugo v0.140.2-aae02ca612a02e085c08366a9c9279f4abb39d94+extended linux/amd64 BuildDate=2024-12-30T15:01:53Z VendorInfo=gohugoio

(removing the links because: An error occurred: Sorry, new users can only put 6 links in a post.)

2

Hi, @andremoreno. Have you tried using the Netlify configuration variable HUGO_VERSION to set the specific version you want to use? If not, would you please give that a try?

3

yes… I already use the HUGO_VERSION

[build.environment]
HUGO_VERSION = “0.140.2”
GO_VERSION = “1.23.4”
HUGO_ENABLEGITINFO = “true”
HUGO_ENV = “production”

this is my netlify.toml : www.andremoreno.id/netlify.toml at master · andremoreno/www.andremoreno.id · GitHub

edit:
I try to redeploy again with Noble. on deploy log when Initializing, i see this line
11:13:20 AM: mise hugo@0.140.2 download hugo_0.140.2_linux-amd64.tar.gz

so I guess it’s not downloading the hugo_extended_0.140.2_linux-amd64.tar.gz file.

or what should I do so I can get the extended version on the Noble build image?

4

I’ve submitted a PR for devs to review. In Noble, it seems we’re currently forcing the standard Hugo version instead of extended.

1 Like
6

This should now be fixed!

7

Thank you for the updates.
But it still not working for me to build with Noble:
I change the HUGO_VERSION to 0.140.0 on my netlify.toml just to make sure the build image reads my netlify.toml

[build.environment]
  HUGO_VERSION = "0.140.0"
  GO_VERSION = "1.23.4"
  HUGO_ENABLEGITINFO = "true"
  HUGO_ENV = "production"
  TZ = "Asia/Jakarta"

2:39:50 PM: ​
2:39:50 PM: ❯ Version
2:39:50 PM:   @netlify/build 29.58.2
2:39:50 PM: ​
2:39:50 PM: ❯ Flags
2:39:50 PM:   accountId: 61311cafdbacc700c3b37f4d
2:39:50 PM:   baseRelDir: true
2:39:50 PM:   buildId: 67821fd9b7b479ecbd85e63b
2:39:50 PM:   deployId: 67821fd9b7b479ecbd85e63d

2:39:50 PM: ​
2:39:50 PM: ❯ Current directory
2:39:50 PM:   /opt/build/repo
2:39:50 PM: ​
2:39:50 PM: ❯ Config file
2:39:50 PM:   /opt/build/repo/netlify.toml
2:39:50 PM: ​
2:39:50 PM: ❯ Context
2:39:50 PM:   production
2:39:50 PM: ​
2:39:50 PM: ❯ Loading plugins
2:39:50 PM:    - netlify-plugin-hugo-cache-resources@0.2.2 from netlify.toml and package.json
2:39:51 PM: Checking if resources exist at "resources"
2:39:51 PM: No cache found for resources folder
2:39:51 PM: ​
2:39:51 PM: build.command from netlify.toml                               
2:39:51 PM: ────────────────────────────────────────────────────────────────
2:39:51 PM: ​
2:39:51 PM: $ hugo --gc --minify
2:39:53 PM: hugo: downloading modules …
2:39:57 PM: hugo: collected modules in 5704 ms
2:39:57 PM: WARN  Module "github.com/gohugoio/hugo-mod-bootstrap-scss/v5" is not compatible with this Hugo version:  extended; run "hugo mod graph" for more information.
2:39:57 PM: Start building sites …

2:39:57 PM: hugo v0.140.0-3f35721fb2c75a1f7cc5a7a14400b66e73d4b06e linux/amd64 BuildDate=2024-12-17T14:20:55Z VendorInfo=gohugoio

the version is like i put on netlify.toml, but still not the extended version.
And this site builds just fine if I use the Focal build image.

8

Looks like the fix has not been rolled out to use. It’s available if I force it on your site, but it should be automatically rolled-out within the coming week.

9

Should be fixed now, mind trying again?

10

yes. it’s working Now. thank you…