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

Setup steps unclear #7

Closed
ignasi35 opened this issue Oct 9, 2015 · 4 comments
Closed

Setup steps unclear #7

ignasi35 opened this issue Oct 9, 2015 · 4 comments

Comments

@ignasi35
Copy link

ignasi35 commented Oct 9, 2015

After cloning the repo I tried to run the tests to ensure my machine fulfilled all requirements. I can't seem to make any test in docker-it-scala pass. I suspect my docker-toolbox installation is somehow not ready to be used by docker-it-scala.

I've seen other issues where a DOCKER_HOST env_var may be set. I've tried 'https://192.168.99.100:2376' without any luck. Any pointers more than welcome.

@viktortnk
Copy link
Contributor

Hi @ignasi35

It utilises configuration from docker-java library.

With my boot2docker setup I have env variables:

export DOCKER_HOST=tcp://192.168.59.103:2376
export DOCKER_CERT_PATH=/Users/viktortnk/.boot2docker/certs/boot2docker-vm
export DOCKER_TLS_VERIFY=1

And inside our ci server we use configuration without SSL

export DOCKER_HOST=tcp://127.0.0.1:2375

(We haven't tested it with communication through socket)

@ignasi35
Copy link
Author

That makes perfect sense. I was executing the tests on a console without any of the env_vars. I migrated recently from boot2docker to docker-machine and those are handled in a less explicit way.

I can run all tests but I'm getting one or two test errors every now and then. They differ from one execution to the other, though. For example:


[error] Error: Total 24, Failed 0, Errors 2, Passed 20, Skipped 2
[error] Error during tests:
[error]     com.whisk.docker.AllAtOnceSpec
[error]     com.whisk.docker.config.ElasticsearchServiceSpec

I'll review in more detail. See if I can isolate the cause (probably my environment again).
Thanks again for the rapid response.

@viktortnk
Copy link
Contributor

No worries. Could you also pull latest changes

@viktortnk
Copy link
Contributor

Closing this. Steps are described in README now

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