-
Notifications
You must be signed in to change notification settings - Fork 325
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
Allow overriding Docker api gem options #509
Conversation
Can one of the admins verify this patch? |
1 similar comment
Can one of the admins verify this patch? |
OK to test |
It would be awesome if you could add a test for the "docker options already set" case |
ok to test |
🔴 Test failed. |
@carlossg The spec tests are failing with your change. Your code assumes that |
@branan on my way back from devops days, didn't forget about it ;) will send fix and test asap |
Do not clean the Docker.options, as they may be already set
Fixed the nil case and added new tests |
💚 Test passed. |
LGTM |
I'll update so that this meets contributor documentation requirements, then it can be merged. |
... not be overridden - as reported in voxpupuli#509 - repackaged PR to meet contributor guidelines
Closing in favor of #520, just pulling in line with contributor doc. |
Do not clean the Docker.options, as they may be already set
Specifically to allow the workaround from upserve/docker-api#202 for
Excon::Errors::SocketError: end of file reached (EOFError)