Skip to content
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

Weird error using jitpack master-SNAPSHOT: #402

Closed
sscarduzio opened this issue Jul 13, 2017 · 5 comments
Closed

Weird error using jitpack master-SNAPSHOT: #402

sscarduzio opened this issue Jul 13, 2017 · 5 comments

Comments

@sscarduzio
Copy link
Contributor

I still have annoyances for test cases that involve more than one container, I was thinking to give a try to the latest updates, and tried to depend on jitpack master snapshot

    compile 'com.github.testcontainers.testcontainers-java:testcontainers:master-SNAPSHOT'

But when I try to build it, I get this non-JVM error I cannot interpret:

:core:test
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /private/var/folders/1k/45f3yx9n5ds8qv13sg_fxr8c0000gn/T/liborg-testcontainers-shaded-netty-transport-native-kqueue2484198301727123789.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /private/var/folders/1k/45f3yx9n5ds8qv13sg_fxr8c0000gn/T/liborg-testcontainers-shaded-netty-transport-native-kqueue2484198301727123789.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

:core:test FAILED

I use MacOS el capitan.

@bsideup
Copy link
Member

bsideup commented Jul 13, 2017

@sscarduzio it's known issue in 1.4.0/1.4.1 with Mac OS X <= 10.11, we're working on a hotfix and will release it ASAP.
Thanks for reporting!

@sscarduzio
Copy link
Contributor Author

Got it. I'm downloading Sierra right now. Never thought something like this would be the thing making me upgrade 😆

@sscarduzio
Copy link
Contributor Author

BTW, just curious, would a simple downgrade in Netty dependencies fix the issue? Do you rely on something Netty introduced in this new version?

@bsideup
Copy link
Member

bsideup commented Jul 13, 2017

@sscarduzio yes, we updated docker-java to the new version with native support of unix socket in Netty and removed our own solution for that, but it works only on 10.12. We're going to fallback to our previous solution if <= 10.11 to provide the best experience for every user :)

@rnorth
Copy link
Member

rnorth commented Jul 15, 2017

Just for visibility, this is the underlying issue: netty/netty#6837

rnorth added a commit that referenced this issue Jul 24, 2017
Adjust docker client provider strategies so that a proxied (TCP) connection is used to connect to the Docker daemon on < OS X 10.12. Fixes #402.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants