Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docker's jekyll/jekyll:pages (and jekyll/jekyll:latest) can't find rake in current setup #84

Open
moutons opened this issue Oct 10, 2017 · 1 comment
Open

docker's jekyll/jekyll:pages (and jekyll/jekyll:latest) can't find rake in current setup #84

moutons opened this issue Oct 10, 2017 · 1 comment

Comments

@moutons
Copy link
Member

moutons commented Oct 10, 2017

jekyll's docker image can't find rake, apparently. I updated the Gemfile because that hasn't been done in a while and apparently this is still a problem?

➜  tirefi.re git:(fix-build) ✗ make fire-up
Recreating tirefire_tirefire_1 ...
Recreating tirefire_tirefire_1 ... done
➜  tirefi.re git:(fix-build) ✗ make fire-logs
Attaching to tirefire_tirefire_1
tirefire_1  | bundler: failed to load command: jekyll (/usr/local/bundle/bin/jekyll)
tirefire_1  | Bundler::GemNotFound: Could not find rake-12.1.0 in any of the sources
tirefire_1  |   /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/spec_set.rb:87:in `block in materialize'
tirefire_1  |   /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/spec_set.rb:81:in `map!'
tirefire_1  |   /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/spec_set.rb:81:in `materialize'
tirefire_1  |   /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/definition.rb:159:in `specs'
tirefire_1  |   /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/definition.rb:218:in `specs_for'
tirefire_1  |   /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/definition.rb:207:in `requested_specs'
tirefire_1  |   /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/runtime.rb:109:in `block in definition_method'
tirefire_1  |   /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/runtime.rb:21:in `setup'
tirefire_1  |   /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler.rb:101:in `setup'
tirefire_1  |   /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/setup.rb:19:in `<top (required)>'
tirefire_1  |   /usr/local/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
tirefire_1  |   /usr/local/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
➜  tirefi.re git:(fix-build) ✗
@moutons
Copy link
Member Author

moutons commented Oct 10, 2017

I say "problem?" because maybe it's time to replace jekyll with something less obviously busted like MS FrontPage or maybe abandon the static site in favor of Joomla or something.

filler pushed a commit that referenced this issue Oct 11, 2017
Call jekyll without bundler
ef5d315 
Per the docs at https://github.com/jekyll/docker, there is no need to
call jekyll via bundler.  There appear to be helper scripts to divine
bundler bits for deps in this project's images now.

This fixes #84 and makes
the tire'est of fires run again for local previewing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@moutons