Gitlab pages with Hugo extended throws core dump on build


Since I am using the extended version of Hugo I can’t just use the gitlab registry image for my gitlab page. I have a docker image with the extended version, which builds the site locally.
However, if I run the page job with a shared runner, hugo works (it prints its version correctly) and starts building the site, but then stops with a core dump.

Anyone experienced something similar or knows how to get an extended log file to see more about the error?

Here is my .gitlab-ci.yml:

image: mashehu/hugo-extended-npm:latest
  - npm ci
  - hugo version
  - hugo
    - public

And here is the runner log:

Running with gitlab-runner 11.1.0 (081978aa)
  on docker-auto-scale fa6cab46
Using Docker executor with image mashehu/hugo-extended-npm:latest ...
Pulling docker image mashehu/hugo-extended-npm:latest ...
Using docker image sha256:1e6e76c7143c72ec6a922dff90b8dfd910aeebc9afcc6869d72055120c5eda64 for mashehu/hugo-extended-npm:latest ...
Running on runner-fa6cab46-project-7536412-concurrent-0 via runner-fa6cab46-srm-1533635251-010205a9...
Cloning repository...
Cloning into '/builds/zencode-itn/sounio'...
Checking out f4cca47b as master...
Updating/initializing submodules recursively...
$ npm ci

> fsevents@1.2.4 install /builds/zencode-itn/sounio/node_modules/fsevents
> node install

added 362 packages in 6.906s
$ hugo version
Hugo Static Site Generator v0.46/extended linux/amd64 BuildDate: 2018-08-01T09:11:41Z
$ hugo
Building sites … /bin/bash: line 70:    38 Segmentation fault      (core dumped) hugo
ERROR: Job failed: exit code 1

I’m running into the same issue. Did you manage to solve it?

Not yet unfortunately. My current solution is to build it locally and push the public folder to gitlab. I could also reproduce the error using a local gitlab-runner. Furthermore, comparing the debug output of Hugo, it seems to break before it uses the PostCSS config, so it could be a problem with the config there (but because i run npm ci it should have all needed packages for the PostCSS step)…