-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to activate fluent-plugin-elasticsearch-5.2.5, because faraday-2.7.4 conflicts with faraday (~> 1.10) (Gem::ConflictError) #1014
Comments
I tried to downgrade the elasticsearch gem to 7.17.7 which is what we were previously using and still get the same error on startup. |
Pinning the install of fluent-plugin-elasticsearch to 5.2.3 gets the pod running but now I get a new error:
This is now the same error as |
Hey @danfinn, my understanding is that while the PR is merged we haven't done a release yet. One thing to note is that I can see you are using |
Unsupported or unmaintained? I think those are 2 different things? Do you know if |
It seems like the suggestion from #984 of installing faraday 1.10.0 has things working again. |
@danfinn Unfortunately it does. https://github.com/Azure/azure-storage-ruby/blob/master/common/azure-storage-common.gemspec#L44. The problem actually lies in the 2nd layer of transitive dependency fluent-plugin-azure-storage-append-blob -> azure-storage-blob -> azure-storage-common. Looks like there's an open issue on the Azure library on this Azure/azure-storage-ruby#225 |
The issue does not appear to be the fluent-plugin-azure-storage-append-blob gem. I removed that from my dockerfile and I still get the same error: /usr/local/lib/ruby/3.1.0/rubygems/specification.rb:2288:in `raise_if_conflicts': Unable to activate fluent-plugin-elasticsearch-5.2.5, because faraday-2.7.4 conflicts with faraday (~> 1.10) (Gem::ConflictError) Here is my Dockerfile that generated this error:
|
Could you use bundle and Gemfile to manage your gem dependencies instead? |
Will be handled to publish this plugin as v5.3.0. |
v5.3.0 has been released so I hope your issue will be solved. |
ok, I will try building again with v5.3.0 |
Unable to activate fluent-plugin-elasticsearch-5.3.0, because faraday-1.10.3 conflicts with faraday (>= 2.0.0), faraday-excon-1.1.0 conflicts with faraday-excon (>= 2.0.0) WTF |
Unable to activate fluent-plugin-elasticsearch-5.3.0, because faraday-1.10.3 conflicts with faraday (>= 2.0.0), faraday-excon-1.1.0 conflicts with faraday-excon (>= 2.0.0) WTF
|
(check apply)
Problem
Recently started seeing this error when starting our fluentd pods. We did recently upgrade the elasticsearch gem from 7.17.7 to 8.6 but I'm nearly sure we weren't seeing this error after making that change.
...
Steps to replicate
Here's our Dockerfile:
Expected Behavior or What you need to ask
the pod to start without errors
Using Fluentd and ES plugin versions
I did also try using FROM fluent/fluentd:v1.16-debian-1 but there was no change there. I saw that there was a PR 3 days ago related to unpinning the version of faraday, perhaps that is related to this?
#1012
The text was updated successfully, but these errors were encountered: