You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using the jekyll/jekyll:3.8 as a base for a Docker image.
In that we run:
RUN gem install jekyll-toc
(our error that we were not installing a specific version)
This morning that started picking up the newly-release v0.17.0 which triggers the following
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux-musl]
Traceback (most recent call last):
21: from /usr/gem/bin/jekyll:23:in `<main>'
20: from /usr/gem/bin/jekyll:23:in `load'
19: from /usr/gem/gems/jekyll-4.2.0/exe/jekyll:8:in `<top (required)>'
18: from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
17: from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
16: from /usr/gem/gems/jekyll-4.2.0/lib/jekyll.rb:195:in `<top (required)>'
15: from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
14: from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
13: from /usr/gem/gems/jekyll-sass-converter-2.0.0/lib/jekyll-sass-converter.rb:4:in `<top (required)>'
12: from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
11: from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
10: from /usr/gem/gems/jekyll-sass-converter-2.0.0/lib/jekyll/converters/scss.rb:3:in `<top (required)>'
9: from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
8: from /usr/local/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
7: from /usr/gem/gems/sassc-2.1.0-x86_64-linux/lib/sassc.rb:31:in `<top (required)>'
6: from /usr/gem/gems/sassc-2.1.0-x86_64-linux/lib/sassc.rb:31:in `require_relative'
5: from /usr/gem/gems/sassc-2.1.0-x86_64-linux/lib/sassc/native.rb:5:in `<top (required)>'
4: from /usr/gem/gems/sassc-2.1.0-x86_64-linux/lib/sassc/native.rb:6:in `<module:SassC>'
3: from /usr/gem/gems/sassc-2.1.0-x86_64-linux/lib/sassc/native.rb:10:in `<module:Native>'
2: from /usr/gem/gems/ffi-1.11.1/lib/ffi/library.rb:99:in `ffi_lib'
1: from /usr/gem/gems/ffi-1.11.1/lib/ffi/library.rb:99:in `map'
/usr/gem/gems/ffi-1.11.1/lib/ffi/library.rb:145:in `block in ffi_lib': Could not open library '/usr/gem/gems/sassc-2.1.0-x86_64-linux/lib/sassc/libsass.so': Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /usr/gem/gems/sassc-2.1.0-x86_64-linux/lib/sassc/libsass.so) (LoadError)
This could be something wrong in our usage/setup, but reporting here for completeness.
The text was updated successfully, but these errors were encountered:
myitcv
added a commit
to play-with-go/play-with-go
that referenced
this issue
Jan 27, 2021
In our base image for the site part of Docker compose, we were running:
RUN gem install jekyll-toc
This installed the latest versio of jekyll-toc at that point in time.
Which is a) clearly not reproducible, and b) liable to be brittle in the
presence of bad new versions.
Exactly that happened this morning with the release of v0.17.0, which
started to give rise to errors reported in:
toshimaru/jekyll-toc#141
This change installs a specific version of that dependency to make this
more resilient.
myitcv
added a commit
to play-with-go/play-with-go
that referenced
this issue
Jan 27, 2021
In our base image for the site part of Docker compose, we were running:
RUN gem install jekyll-toc
This installed the latest versio of jekyll-toc at that point in time.
Which is a) clearly not reproducible, and b) liable to be brittle in the
presence of bad new versions.
Exactly that happened this morning with the release of v0.17.0, which
started to give rise to errors reported in:
toshimaru/jekyll-toc#141
This change installs a specific version of that dependency to make this
more resilient.
We are using the
jekyll/jekyll:3.8
as a base for a Docker image.In that we run:
(our error that we were not installing a specific version)
This morning that started picking up the newly-release v0.17.0 which triggers the following
This could be something wrong in our usage/setup, but reporting here for completeness.
The text was updated successfully, but these errors were encountered: