This repository has been archived by the owner on Jul 27, 2021. It is now read-only.
This repository has been archived by the owner on Jul 27, 2021. It is now read-only.
Unable to start container sqlite3 gem #15
Open
Description
Replicated this issue on both Fargate and local machine when starting a container:
+ RAILS_ENV=production
+ rake assets:precompile
rake aborted!
LoadError: libsqlite3.so.0: cannot open shared object file: No such file or directory - /usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3/sqlite3_native.so
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:6:in `require'
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:6:in `rescue in <top (required)>'
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:2:in `<top (required)>'
/usr/src/app/config/application.rb:7:in `<top (required)>'
/usr/src/app/Rakefile:4:in `<top (required)>'
/usr/local/bundle/gems/rake-12.3.1/exe/rake:27:in `<top (required)>'
Caused by:
LoadError: cannot load such file -- sqlite3/2.5/sqlite3_native
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:4:in `require'
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:4:in `<top (required)>'
/usr/src/app/config/application.rb:7:in `<top (required)>'
/usr/src/app/Rakefile:4:in `<top (required)>'
/usr/local/bundle/gems/rake-12.3.1/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)
+ exec rails s -e production -b 0.0.0.0
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:6:in `require': libsqlite3.so.0: cannot open shared object file: No such file or directory - /usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3/sqlite3_native.so (LoadError)
from /usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:6:in `rescue in <top (required)>'
from /usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:2:in `<top (required)>'
from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:81:in `require'
from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:81:in `block (2 levels) in require'
from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:76:in `each'
from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:76:in `block in require'
from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:65:in `each'
from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:65:in `require'
from /usr/local/lib/ruby/site_ruby/2.5.0/bundler.rb:114:in `require'
from /usr/src/app/config/application.rb:7:in `<top (required)>'
from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:78:in `require'
from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:78:in `block in server'
from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:75:in `tap'
from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:75:in `server'
from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands.rb:17:in `<top (required)>'
from /usr/src/app/bin/rails:9:in `require'
from /usr/src/app/bin/rails:9:in `<top (required)>'
from /usr/local/bundle/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `load'
from /usr/local/bundle/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `call'
from /usr/local/bundle/gems/spring-2.0.2/lib/spring/client/command.rb:7:in `call'
from /usr/local/bundle/gems/spring-2.0.2/lib/spring/client.rb:30:in `run'
from /usr/local/bundle/gems/spring-2.0.2/bin/spring:49:in `<top (required)>'
from /usr/local/bundle/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `load'
from /usr/local/bundle/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `<top (required)>'
from /usr/local/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:65:in `require'
from /usr/local/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:65:in `require'
from /usr/src/app/bin/spring:13:in `<top (required)>'
from bin/rails:3:in `load'
from bin/rails:3:in `<main>'
I was able to temporarily solve the issue by using the base ruby2.5 image (without the -slim) and it works fine with:
FROM ruby:2.5
Not 100% sure on the best way forward yet, as I'm a fan of keeping images small, so would like to keep using slim, just raising this for visibility and in-case it helps someone.
Metadata
Assignees
Labels
No labels
Activity