I have looked at the jboss-docker pages.
This is all good, but not of much help in building, packaging and moving whole envionments from test to production.
My question is how to use containers as the unit of deployment combined with jBoss domain mode.
1 of 1 people found this helpful
We're still ramping up with docker in the JBoss middleware team, I don't know that there has been a lot of thought given to using EAP in domain mode when bundled in docker images. I'm interested in your use case.
The domain model is all about managing the common configuration of multiple instances of EAP across multiple servers. Docker is also used to manage the configuration of multiple instances, but with a very different model. The entire stack is defined in your final docker image, including applications and configuration. What do you intend to use the domain model for once you have multiple instances of EAP running in containers?
Im starting to realize this myself.
I was hoping there were plans for a best of both-soloution, for instance lettting the nodes control deployment on registering in the domain.
For now I think I will continue my testing using standalone servers and keeping mod_cluster in front.