Issue with the containers when trying to build Linaro/ecosystemlandscape project

[laggarcia]

Following the instructions on the Linaro/ecosystemlandscape project, I run the build-site.sh script to build the static site. I get the following error.

laggarcia@fedora:~/src/git/ecosystemlandscape$ ./build-site.sh 
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Container built by GitHub. Build reference: db922be
Single-repo site - proceeding with normal processing.
Cannot find Gemfile in source directory

Looking at the command line that started the container inside the build-site.sh script, we have something like this:

laggarcia@fedora:~/src/git/ecosystemlandscape$ JEKYLL_ENV="production" docker run --cap-drop ALL --rm -t -i -e JEKYLL_ENV -v /etc/passwd:/etc/passwd:ro -v /etc/group:/etc/group:ro -u "1000":"1000" -v "/home/laggarcia/src/git/ecosystemlandscape":/srv/source linaroits/jekyllsitebuild:"latest" build-site.sh ""
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Container built by GitHub. Build reference: db922be
Single-repo site - proceeding with normal processing.
Cannot find Gemfile in source directory

The error message is complaining that it could not find the Gemfile in source directory. However, the volume mapping in the command line ("/home/laggarcia/src/git/ecosystemlandscape":/srv/source) is correct, at least from the point of view of the host environment, as /home/laggarcia/src/git/ecosystemlandscape is the source directory where the GemFile is present. I have very little experience with containers, so I wasn't able to verify the contents of the container image (even if I try to start the container with a /bin/bash process I get the same error, probably because some container initialization script is trying to read the Gemfile before the process from the command line is called inside the container).

Reading the documentation, I see that this project has been tested on many distros, but not Fedora. And Fedora is the distro I am using. Hence, I thought this would be selinux blocking the access to the Gemfile. I looked at the journal and the selinux log, but there are no error messages there when I start the container.

Any help on debugging this issue would be appreciated.