roboconf / roboconf-platform

The core modules and the platform
Apache License 2.0
35 stars 11 forks source link

Roboconf is not working with Docker 1.12+ #687

Closed cdeneux closed 8 years ago

cdeneux commented 8 years ago

Roboconf is not working with Docker 1.12+ :

2016-09-12 12:46:42,575 | DEBUG | DockerUtils                      | Found a Docker image with tag roboconf-tomcat8
2016-09-12 12:46:42,575 | INFO  | DockerMachineConfigurator        | Creating container rbcf_c361cfd3-ad2f-4f1c-813f-3a9d679942a0 from image roboconf-tomcat8
2016-09-12 12:46:42,722 | ERROR | edTargetHandler$CheckingRunnable | An error occurred while configuring machine 'rbcf_c361cfd3-ad2f-4f1c-813f-3a9d679942a0'. com.github.dockerjava.api.BadRequestException: {"message":"starting container with HostConfig was deprecated since v1.10 and removed in v1.12"}

2016-09-12 12:46:42,722 | ERROR | edTargetHandler$CheckingRunnable | An error occurred while configuring machine 'rbcf_c361cfd3-ad2f-4f1c-813f-3a9d679942a0'. com.github.dockerjava.api.BadRequestException: {"message":"starting container with HostConfig was deprecated since v1.10 and removed in v1.12"}

2016-09-12 12:46:42,723 | DEBUG | edTargetHandler$CheckingRunnable | Closing the configurator for machine rbcf_c361cfd3-ad2f-4f1c-813f-3a9d679942a0
vincent-zurczak commented 8 years ago

OK. I reproduced the problem. I updated our Docker-Java library. I successfully tested it on my machine (Docker 1.12.1).

Could you verify it also works on your side? You can get the code on my fork. I will wait for your feedback before submitting a PR.

vincent-zurczak commented 8 years ago

Be careful, your Docker end-point must now start with tcp://. The documentation of the snapshot version was updated.

cdeneux commented 8 years ago

Sorry but the bulid fails:

Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/plugin-tools/maven-plugin-tools-api/3.3/maven-plugin-tools-api-3.3.jar (23 KB at 22.7 KB/sec)
[INFO] Using 'UTF-8' encoding to read mojo metadata.
[INFO] Applying mojo extractor for language: java
[INFO] Mojo extractor for language: java found 0 mojo descriptors.
[INFO] Applying mojo extractor for language: bsh
[INFO] Mojo extractor for language: bsh found 0 mojo descriptors.
[INFO] Applying mojo extractor for language: java-annotations
[INFO] Mojo extractor for language: java-annotations found 0 mojo descriptors.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Roboconf :: Platform Parent ....................... SUCCESS [1.971s]
[INFO] Roboconf :: Core .................................. SUCCESS [14.451s]
[INFO] Roboconf :: Deployment Manager :: Web Administration  SUCCESS [12.089s]
[INFO] Roboconf :: Target :: API ......................... SUCCESS [9.268s]
[INFO] Roboconf :: Plugin :: API ......................... SUCCESS [0.761s]
[INFO] Roboconf :: Messaging :: API ...................... SUCCESS [4.405s]
[INFO] Roboconf :: Agent :: Monitoring API ............... SUCCESS [0.502s]
[INFO] Roboconf :: Tooling Core .......................... SUCCESS [1.524s]
[INFO] Roboconf :: Documentation Generator ............... SUCCESS [1:00.431s]
[INFO] Roboconf :: Maven Plug-in ......................... FAILURE [13.982s]
[INFO] Roboconf :: Messaging :: Rabbit MQ ................ SKIPPED
[INFO] Roboconf :: Messaging :: HTTP ..................... SKIPPED
........
[INFO] Roboconf :: Deployment Manager :: REST Client ..... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:37.087s
[INFO] Finished at: Wed Sep 14 09:23:25 CEST 2016
[INFO] Final Memory: 62M/275M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-plugin-plugin:3.3:descriptor (default-descriptor) on project roboconf-maven-plugin: Error extracting plugin descriptor: 'No mojo definitions were found for plugin: net.roboconf:roboconf-maven-plugin.' -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :roboconf-maven-plugin
vincent-zurczak commented 8 years ago

There was indeed a bug. But it was not the Maven plug-in that failed. There was a conflict in the class path of the Docker target. I cleared my Maven repo and performed a full build, including integration tests and manual tests. Everything passed.

Could you make a new try please?

cdeneux commented 8 years ago

Same error with a full build executed with a cleaned repository.

My maven installation is:

Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 17:22:22+0200)
Maven home: /home/cdeneux/maven
Java version: 1.8.0_91, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-36-generic", arch: "amd64", family: "unix"
vincent-zurczak commented 8 years ago

OK. I am using Java 7. I will try with Java 8. :confused:

cdeneux commented 8 years ago

The build is ok using Maven 3.3.9