The discussion revolves around resolving a Gem::ConflictError when running Sidekiq. Overgrow initially encountered the issue, with a conflict between rack-1.6.4 and rack (~> 2.0), and attempted to resolve it by running bundle install. However, the issue persisted.
Overgrow eventually solved the problem by downgrading Sidekiq to version 4.1.2. However, another error occurred due to a conflict between activesupport versions.
Eviltrout suggested that instead of installing Sidekiq separately, it should be run using bundle exec sidekiq, which uses the version specified in the project’s Gemfile. This solution was successful, as confirmed by Overgrow.
Hi, I’ve stumbled upon this issue, hard to tell what I’ve done wrong and changed in the process. My sidekiq was working well but suddenly I can’t start it…
overgrow@axii:~/discourse$ sidekiq
/home/overgrow/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:2288:in `raise_if_conflicts’: Unable to activate actionpack-5.0.0, because rack-1.6.4 conflicts with rack (~> 2.0) (Gem::ConflictError)
overgrow@axii:~/discourse$ gem list --local | grep rack
rack (2.0.1, 1.6.4)
overgrow@axii:~/discourse$ gem list --local | grep actionp
actionpack (5.0.0, 4.2.7)
Finally… Solved.. I have downgraded sidekiq to 4.1.2
gem uninstall sidekiq
gem install sidekiq --version '<=4.1.2'
/home/carlos/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:35:in block in setup': You have already activated activesupport 5.0.0, but your Gemfile requires activesupport 4.2.7. Prepending bundle exec` to your command may solve this. (Gem::LoadError)