Is this project dead???

[jimklo]

It seems like @envygeeks hasn't done anything in over a year while issues and pull requests pile up and go stale or folks just close pull requests as they become dated.

I feel this project is dead, which is unfortunate, since the main jekyll project references this docker-container. Worse is there isn't really enough documentation to figure out how to build the images for different architectures, given the popularity of Apple Silicon and Raspberry Pi - the current build doesn't work on M2 (cannot build eventmachine for amd64 under Rosetta).

Has anyone made fork that works? Does anyone have an alternative solution?

Thanks,

/jk

[JV-conseil]

Hi 👋

While waiting for @envygeeks to update this repo, I've pushed to Docker Hub an updated version for jekyll/builder image: https://hub.docker.com/r/jvconseil/jekyll-docker

See also PR https://github.com/envygeeks/jekyll-docker/pull/369

Best, @JV-conseil

[jimklo]

@JV-conseil unfortunately I went ahead and just defined my own Dockerfile and entrypoint.sh that is much simpler than what this container provides, but functions mostly in a compatible way.

[akc42]

@JV-conseil I came here looking for why my project with this image failed to build and ended up trying yours. Worked perfectly. Thank you

[rockstorm101]

Has anyone made fork that works? Does anyone have an alternative solution?

Probably a bit late to the party here but I've been successfully using a different approach. Other than using these pre-built images I generate a custom image for each blog/site that won't need to be updated unless you change any dependencies. This way you build your image once and it runs fast, smooth and reliably every time afterwards. No need to re-install any gems or anything every time you build your blog. See https://github.com/rockstorm101/jekyll-docker