The docker plugin configuration has been moved to the subprojects and
the configuration adapted accordingly.
If no linking is required between Docker containers, the prefered way
to configure this plugin is within submodules. Currently there is
quite some redundancy, this is currently unavoidable. Latter on the
dmp might be enhanced to allow for some templating in the
configuration.
Some remarks about the base image jboss/wildfly:
It's quite bloated. For a Mircorservice base image serving as runtim
it shouldn't contain exampls and documentation.
Since it is assumed to runder a fix user id "jboss" problem will
arise within a OpenShift since there a container is run by default
under a random UID for security reason. The problem will be that
this random user is not allowed to write in the deployment
directory
See here for more about information about the OpenShift decision:
https://docs.openshift.org/latest/creating_images/guidelines.html#openshift-specific-guidelines
The admin console doesn't work since it doesn't seem to be prepared
to be run within a Docker image
I had to make some minor fixes for the Docker Maven Plugin, since up
to now it was not tested very well in a multi-module-project. So
currently 0.12.1-SNAPSHOT is used, but I will make a release at the
end of this week for 0.12.1
The configuration of the plugin also has been moved out of the
profile, since it doesn't harm anyway. I left the binding to execution
phases in the profile, though.
You can now build the images with
mvn package docker:build
(package is required because of a Maven limitation, otherwise the
assembly can't find its artefact) and start it with
mvn docker:start
This can be done also in a single subproject. A new, quite cool
feature is 'mvn docker:watch' so when you call
in one terminal (it will block) and then change and compile any
subproject, the Docker image will automatically be rebuilt and
restarted. This only works from within a subproject and not top-level
because it blocks.
The docker plugin configuration has been moved to the subprojects and the configuration adapted accordingly.
If no linking is required between Docker containers, the prefered way to configure this plugin is within submodules. Currently there is quite some redundancy, this is currently unavoidable. Latter on the dmp might be enhanced to allow for some templating in the configuration.
Some remarks about the base image jboss/wildfly:
I had to make some minor fixes for the Docker Maven Plugin, since up to now it was not tested very well in a multi-module-project. So currently 0.12.1-SNAPSHOT is used, but I will make a release at the end of this week for 0.12.1
The configuration of the plugin also has been moved out of the profile, since it doesn't harm anyway. I left the binding to execution phases in the profile, though.
You can now build the images with
(package is required because of a Maven limitation, otherwise the assembly can't find its artefact) and start it with
This can be done also in a single subproject. A new, quite cool feature is 'mvn docker:watch' so when you call
in one terminal (it will block) and then change and compile any subproject, the Docker image will automatically be rebuilt and restarted. This only works from within a subproject and not top-level because it blocks.