Which maven repository has this jar file? I used the following in my pom.xml:

Hi. It seems that there is no way to connect to docker with secured connection (which is default for boot2docker). It could be switched off, but is strictly unrecommended by them. I mean it would be great to expose details of docker client creation, to enable constructions like
final DockerClient docker = new DefaultDockerClient.builder()
.uri(URI.create("https://boot2docker:2376"))
.dockerCertificates(new DockerCertificates("/Users/rohan/.docker/boot2docker-vm/"))
.build();

Hi,

Is there any plan or roadmap of when users can expect newer Overcast versions to be released into the Maven Central?

Hello @xebialabs Team,

Do you plan to have new Overcast version released to Maven Central any time soon? We are working on SNAPSHOT versions since Jun 2015 (more than 2 years now) because some important fixes has not yet been released to Central repo (but are available in the code) :( If newest code (with updated dependencies) cannot be released, then can we count on version 1.5.2 at c712360?

I would like to have Overcast updated because new version is required in my overcast-maven-plugin which I would like to use in a demo of Overcast on the JUG event (Java Users Group meetup) so other people can learn about this awesome tool, that is the Overcast.

Please let me know it this is feasible. If not then I will have to release it on my own under my group ID, but I would really like to avoid it since I (and probably other users as well) prefer to have only one and valid source of Overcast dependencies in Maven Central.

please please make it APACHE 2.0 :)

Support for running tests against docker-compose files would be a hugely compelling feature.
With support for docker-compose there should be little need for custom config files for docker.

Please consider adding docker-compose support

Hi, I have to start my testcontainer with the -t flag. Otherwise the container will stop with errors. Will create a pull request for that feature.

Hello @xebialabs team,

Overcast is using pretty old Docker Client which disallow use of Unix socket when communicating with Docker REST interface. The one currently used is 2.4.2 but I verified 2.7.6 to work perfectly well. By overriding this dependency with newer one I was able to spawn new containers without reconfiguring my Docker daemon to listen on TCP port. Also, with newer Docker Client my Overcast configuration utilizes unix:// socket protocol and working just fine without any additional changes in the Overcast code.

Example:

mysql {
    dockerHost="unix:///var/run/docker.sock"
    dockerImage="mysql:5.6"
    exposeAllPorts=true
    remove=true
    env=["MYSQL_ROOT_PASSWORD=foo","MYSQL_USER=root","MYSQL_DATABASE=bar"]
    command=["mysqld"]
}

Please consider upgrading to newer Docker Client.

com.spotify:docker-client introduced quite a lot of old dependencies that clash with XL platform
Take a look if they can be excluded / updated

Hey guys!

Any plans for new minor release? Quite a few features have been introduced :)
Thanks!

Best Regards,
Andriy Redko