-
-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Image for 4.2.2 broken #340
Comments
I hit the same problem with the I see this missing webrick dependency issue is also filed as #335. |
On Sunday, 8 May 2022 17:46:54 GMT Gerard Ryan wrote:
I hit the same problem with the `jekyll serve`, but I was able to work
around it by adding `gem "webrick", "~> 1.7"` to my Gemfile.
Thanks, I'll test it later. That said, this is not a solution, as even `jekyll
new` fails.
…--
Best,
r
|
Hopefully we will see a solution now that Jekyll 4.3.0 has been released: In the Jekyll 4.3.0 release notes:
So hopefully a fix is as simple as updating these images to use Jekyll 4.3.0. |
@grdryn Creating a Gemfile results in the container not having access to it, how did u solve that ?
|
solved, this one was caused by the docker desktop for Mac mount protection |
Looks like I've stumbled into a bit of a ... maintenance issue. The oldest reference to this exact same issue I could find is #335 which is for some reason "locked and limited to collaborators". It's from Apr 12, 2022 and predates this one by a month. Then there are also
There hasn't been a commit on this project since Apr 20, 2022 and this is really just an issue of a missing Gem, I doubt that this will be fixed any time soon. Unfortunate, but that is sometimes the reality of open source software. It's free but comes with some caveats. |
When I use the image I run it this way:
|
Yes, workarounds for this particular issue are easy. But that doesn't change the fact that they are workarounds and that the project seems to be unmaintained. I'm currently looking into https://github.com/BretFisher/jekyll-serve which works as-is. Or maybe I'll just end up rolling my own Docker image since that is not very difficult and I now had to learn about Jekyll's inner workings anyway :) |
And please don't get me wrong here. This is not a "complaint". I know how much time and effort it takes to maintain an open source project. I don't blame anyone for not finding the time to constantly update this and that and dealing with issues and support. It's a lot to ask for free. |
@envygeeks it would be amazing if you can find some time to rebuild and post the docker image so everyone can enjoy patched v4. If you want, I can PR a GH action that will autorelease if git tag is set. |
Docker image for Jekyll 4.2.2 is badly broken. Consider:
Trying
serve
on an existing Jekyll project (cleanly created withjekyll new
executed outside of container):Everything works just fine on v4.2.0 (there seems to be no v4.2.1 on Docker Hub):
Effectively, the v4.2.2 image is unusable.
The text was updated successfully, but these errors were encountered: