search

arc42 / quality.arc42.org-site

Quality requirements and goals for software and system architectures
https://quality.arc42.org
Other
21 stars 12 forks source link

Local docker-compose fails with `check_for_activated_spec` #150

Closed PapaBravo closed 7 months ago

PapaBravo commented 7 months ago

When running docker-compose up on the current (d4f4036285d3d234eb3bce2a2bc37c0e870ce54c) main branch, the serve command fails with the following error message

...
Starting qualityarc42org-site_jekyll_1 ... done
Attaching to qualityarc42org-site_jekyll_1
jekyll_1  | ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236) [x86_64-linux-musl]
jekyll_1  | /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler/runtime.rb:308:in `check_for_activated_spec!': You have already activated public_suffix 5.0.0, but your Gemfile requires public_suffix 4.0.7. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)
jekyll_1  |     from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler/runtime.rb:25:in `block in setup'
jekyll_1  |     from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler/spec_set.rb:155:in `each'
jekyll_1  |     from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler/spec_set.rb:155:in `each'
jekyll_1  |     from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler/runtime.rb:24:in `map'
jekyll_1  |     from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler/runtime.rb:24:in `setup'
jekyll_1  |     from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler.rb:161:in `setup'
jekyll_1  |     from /usr/gem/gems/jekyll-4.2.2/lib/jekyll/plugin_manager.rb:52:in `require_from_bundler'
jekyll_1  |     from /usr/gem/gems/jekyll-4.2.2/exe/jekyll:11:in `<top (required)>'
jekyll_1  |     from /usr/gem/bin/jekyll:25:in `load'
jekyll_1  |     from /usr/gem/bin/jekyll:25:in `<main>'
qualityarc42org-site_jekyll_1 exited with code 1

Following the hint in the error message fixes the issue. Using bundle exec jekyll serve is shown on the jekyll blog and recommended in this stackoverflow answer. PR for the simple fix is following shortly.