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.

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

Can't install Bootstrap gem #329

Open
frederikheld opened this issue Jan 18, 2022 · 2 comments
Open

Can't install Bootstrap gem #329

frederikheld opened this issue Jan 18, 2022 · 2 comments

Comments

@frederikheld
Copy link

frederikheld commented Jan 18, 2022

Hey everyone,

I tried to add Bootstrap to my Jekyll project via the Gemfile. When using the jekyll/jekyll or jekyll/builder image, this leads to the following error:

/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/runtime.rb:319:in `check_for_activated_spec!': You have already activated concurrent-ruby 1.1.5, but your Gemfile requires concurrent-ruby 1.1.9. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)

So I tried the jekyll/minimal image but it failed as well because the minimal image doesn't support C based gems.

So what else can I do?

Thanks in advance
Fred

@frederikheld
Copy link
Author

frederikheld commented Jan 18, 2022

Running the jekyll/minimal image like this:

docker run --rm --volume "$PWD:/srv/jekyll" -p 4000:4000 --env JEKYLL_ENV=development jekyll/minimal:3.8 sh -c "apk add libc-dev g++ make && jekyll serve --future -s src"

fixed the missing support for C based gems. But it brought me back to the initial error.

The error message says

Prepending `bundle exec` to your command may solve this.

So where do I need to add this?

@frederikheld
Copy link
Author

Adding bundle exec before jekyll serve leads to another error:

/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/spec_set.rb:87:in `block in materialize': Could not find rake-13.0.6 in any of the sources (Bundler::GemNotFound)

Did I mention that I have no idea how Ruby works (that's why I wanted to lock it away in a container in the first place) and that I hate to learn the very specific errors of a new language to be able to use it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant