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

Can't get the plugin working with Boot2Docker #22

Open
johanhaleby opened this issue Dec 6, 2014 · 2 comments
Open

Can't get the plugin working with Boot2Docker #22

johanhaleby opened this issue Dec 6, 2014 · 2 comments

Comments

@johanhaleby
Copy link

I'm new to docker so I'm sorry if I'm missing something trivial. Anyway I'm using Boot2Docker v1.3.2 and running docker version gives me the following:

Client version: 1.3.2
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): 39fa2fa
OS/Arch (client): darwin/amd64
Server version: 1.3.2
Server API version: 1.15
Go version (server): go1.3.3
Git commit (server): 39fa2fa

The problem is that when I run the following:

lein uberimage -H http://192.168.59.104:2376

I get the following error:

#<IOException java.io.IOException: This archives contains unclosed entries.>
Dec 06, 2014 6:43:32 AM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: I/O exception (java.net.SocketException) caught when processing request to {}->http://192.168.59.104:2376: Broken pipe
Dec 06, 2014 6:43:32 AM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: Retrying request to {}->http://192.168.59.104:2376
java.net.SocketException: Broken pipe

If I SSH into the docker container (using boot2docker ssh) can check the the /var/lib/boot2docker/docker.log file the following error shows up:

2014/12/05 20:35:52 http: TLS handshake error from 192.168.59.3:61556: tls: oversized record received with length 21536

I've also tried changing to https but it gives me the following error when using leiningen:

Using jar file /Users/johan/devtools/java/projects/parkster/code/backend/bad-email-notifier/ target/uberjar /bad-email-notifier-0.1.0-SNAPSHOT-standalone.jar
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
 at sun.security.provider.certpath.SunCertPathBuilder.build (SunCertPathBuilder.java:145)
    sun.security.provider.certpath.SunCertPathBuilder.engineBuild (SunCertPathBuilder.java:131)
    java.security.cert.CertPathBuilder.build (CertPathBuilder.java:280)

and the following in the /var/lib/boot2docker/docker.log file:

2014/12/05 20:36:42 http: TLS handshake error from 192.168.59.3:61557: remote error: unknown certificate

I'm not sure how to proceed.

@hugoduncan
Copy link
Member

Looks like you should be using https, but that we need to either specify the certificate, or that the certificate doesn't need checking.

@johanhaleby
Copy link
Author

Yes I think so as well. I found a workaround here. What you can do is running:

$(docker run sequenceiq/socat)

Then it'll start the a proxy on port 2735 and the plugin will work just fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants