Github pages build fails with weird error

Help
1

Hello,
my GH Pages build fails with this error message.
My Gemfile is only the default:

source "https://rubygems.org"
gem "github-pages", group: :jekyll_plugins

I only use plugins supported officially by Github, such as jekyll-feed or jekyll-seo-tag.

Can anybody help with this error? Thank you in advance.

2

can you share your repo?

is this a new site or just random started happening to an existing site?

3

If you are using standard GH pages flow, you don’t get to install anything (it ignores your Gemfile and just uses plugins and theme in config)

With that level of detail my guess is you are using a workflow on Github Actions - is that correct?

A permission issue locally with bundle is often because its not configured for the project. So use this locally and on the remote if using actions

bundle config --local path vendor/bundle 
bundle install

If you use the right action it will take care of that for you.

4

That is true, I’m using the default Github Action for Jekyll Pages. This is the workflow file:

name: Jekyll site CI

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

jobs:
  build:

    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2
    - name: Build the site in the jekyll/builder container
      run: |
        docker run \
        -v ${{ github.workspace }}:/srv/jekyll -v ${{ github.workspace }}/_site:/srv/jekyll/_site \
        jekyll/builder:latest /bin/bash -c "chmod 777 /srv/jekyll && jekyll build --future"

Locally, I can run bundle exec jekyll build without any problems, the error only occurs when running via Github Actions.

How do I execute the commands you provided in Github Actions? Isn’t the Action provided by Github supposed to be correct?

5

I am not familiar with that one. I also can’t see where the install happens or how the result is stored.

Can you find a demo or other project which successfully runs using the workflow above and then see if you are doing something different?

You can also swop out workflow. Here is a demo I wrote while creating a manual for jekyll docs. It uses “jekyll actions” linked as a badge in my readme. So I didn’t haven’t to so any docker commands directly.

6

Also mine runs on master and builds to gh-pages branch by the way.

7

I fixed it by simply removing the Github action. Of course, maybe it can be fixed by looking deeper into the script, but I can’t be bothered at the moment.