Jordon Bedwell

We don't build our images for Arm, only x86/64

This image adheres to security best practices, that's why the `jekyll` user exists. The root at boot is necessary and required so that the image can adjust permissions and install...

You don’t need the root:root as well drop permissions ourselves when we build.

It would seem this issue applies to 2.5, 2.6 & 2.6 https://bugs.ruby-lang.org/issues/16965 on that the current image does indeed have Ruby 2.7, we don't generally update past images with newer...

There isn't much I can do about that error unfortunately. It's mostly up to RedHat to either fix it in the Kernel, or Ruby to fix it.

In theory `jekyll` should still be loading your `_config.yml` if it's in the default (root) location of your source because that's the file it looks for by default if it...

Is there a bug here?

If it's included inside of your Jekyll Root we'll pick it up! On a side note there is a plan to migrate to Ubuntu eventually sometime soon, but I have...

This is a pretty well known issue with Jekyll, and Docker on Windows. I'm not against adding it, but I don't know how you're using Docker or Windows to even...

Docker Hub is incapable of building dynamic images. I am not against building a master template though, and fixing Travis-CI to rebuild the image, or moving to Github Actions, I...