You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to use shiplift in a circleci environment with hyper, it must use tcp to connect to the remote docker daemon. This requires tls via the docker docs. The issue arises here https://github.com/softprops/shiplift/blob/master/src/transport.rs#L166 when the tcp:// scheme is copied. The real problem is that hyper's version checking requires the use of https instead of tcp directly. Thus the fix here is to replace the scheme only when encrypted.
When attempting to use shiplift in a circleci environment with hyper, it must use
tcp
to connect to the remote docker daemon. This requires tls via the docker docs. The issue arises here https://github.com/softprops/shiplift/blob/master/src/transport.rs#L166 when thetcp://
scheme is copied. The real problem is that hyper's version checking requires the use ofhttps
instead oftcp
directly. Thus the fix here is to replace the scheme only when encrypted.Reference failing tests in vectordotdev/vector#787
The text was updated successfully, but these errors were encountered: