slimtoolkit / slimtoolkit/slim
Minified Rails/Unicorn startup failure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
config.ru:1:in <main>': cannot load such file -- rack/builder (LoadError) from /usr/local/bundle/gems/unicorn-4.9.0/lib/unicorn.rb:48:ineval'
from /usr/local/bundle/gems/unicorn-4.9.0/lib/unicorn.rb:48:in block in builder' from /usr/local/bundle/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:768:incall'
from /usr/local/bundle/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:768:in build_app!' from /usr/local/bundle/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:137:instart'
from /usr/local/bundle/gems/unicorn-4.9.0/bin/unicorn:126:in <top (required)>' from /usr/local/bundle/bin/unicorn:16:inload'
from /usr/local/bundle/bin/unicorn:16:in `
Reported in this blog post:
http://chrisstump.online/2016/02/23/docker-image-reduction-techniques-and-tools/
Similar Rails app:
https://github.com/cstump/docker_example
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the similar Rails app linked in the issue and inspect config.ru alongside the Unicorn startup trace. Determine why the minified image cannot load rack/builder; done means the Rails/Unicorn application starts successfully from the minified image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rails, ruby
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100