Public | Automated Build

Last pushed: 4 days ago
Short Description
A basic container containing just Jekyll. Can run serve, but by default does nothing. Extremely easy to use. Makes no assumptions.
Full Description

Simple Docker Container for Jekyll Work

Use example:

sudo docker run --rm -v "$(pwd):/src" grahamc/jekyll build

or for repeated calls:

alias jekyll='sudo docker run --rm -v "$(pwd):/src" grahamc/jekyll'
jekyll build
jekyll serve

run as a server:

sudo docker run -d -v "$(pwd):/src" -p 4000:4000 grahamc/jekyll serve

Goodies

  • Supports pygments syntax highlighting
  • Supports RDiscount
  • Supports Kramdown
Docker Pull Command
Owner
grahamc
Source Repository

Comments (6)
xevaquor
a year ago

If you will have issues like

Conversion error: Jekyll::Converters::Scss encountered an error while converting '/css/main.scss':
Invalid US-ASCII character "\xC4" on line 38

Add -e "LC_ALL=C.UTF-8" switch

stenio123
2 years ago

In the github page of this project, the last command is slightly different than what is shown here. Using this updated version was the only way I got it to work:

sudo docker run -d -v "$PWD:/src" -p 4000:4000 grahamc/jekyll serve -H 0.0.0.0

Thank you!

gektorgrom
2 years ago

Hi, just stupid question. Could I use jekyll build with -destination option "/home/user/..."?

mrcoder
2 years ago

Thanks for the image. I have got an error when running it with boot2docker on Macbook Pro. I have asked the question here (http://stackoverflow.com/questions/30666698/error-when-running-jekyll-docker-container-with-boot2docker-on-mac). Could you please help me out? The console with error message looks like:

twer$ $(boot2docker shellinit 2> /dev/null)
twer$ docker run --rm -v "$PWD:/src" grahamc/jekyll build
/usr/local/bundle/gems/bundler-1.9.9/lib/bundler/spec_set.rb:92:in `block in materialize': Could not find coffee-script-source-1.9.1 in any of the sources (Bundler::GemNotFound)
from /usr/local/bundle/gems/bundler-1.9.9/lib/bundler/spec_set.rb:85:in `map!'
from /usr/local/bundle/gems/bundler-1.9.9/lib/bundler/spec_set.rb:85:in `materialize'
from /usr/local/bundle/gems/bundler-1.9.9/lib/bundler/definition.rb:132:in `specs'
from /usr/local/bundle/gems/bundler-1.9.9/lib/bundler/definition.rb:177:in `specs_for'
from /usr/local/bundle/gems/bundler-1.9.9/lib/bundler/definition.rb:166:in `requested_specs'
from /usr/local/bundle/gems/bundler-1.9.9/lib/bundler/environment.rb:18:in `requested_specs'
from /usr/local/bundle/gems/bundler-1.9.9/lib/bundler/runtime.rb:13:in `setup'
from /usr/local/bundle/gems/bundler-1.9.9/lib/bundler.rb:122:in `setup'
from /usr/local/bundle/gems/jekyll-2.5.3/lib/jekyll/plugin_manager.rb:37:in `require_from_bundler'
from /usr/local/bundle/gems/jekyll-2.5.3/bin/jekyll:16:in `<top (required)>'
from /usr/local/bundle/bin/jekyll:23:in `load'
jhabdas
2 years ago

Thanks for opening this up. Has the jekyll-redirect-from gem been working well for you? CloudFlare offers 3 wildcard redirects for free but offloading some of that effort to a plug-in should open up slots on the CDN for things like TLD 301s.

For those not using GitHub pages for hosting, here's a Jekyll seed to help you get going with your own hosting provider.

newtmitch
3 years ago

Trying this out now - glad to see it's here! Your "background daemon" CLI has conflicting commands: the -d and --rm. I think you meant to remove the "--rm".