Default configuration is a great place to start with a project. We at JBoss try
to make our projects (and
products too!) usable out-of-box for as
many use cases as we can, but there is no way that one configuration could
satisfy everyone’s needs. For example, we ship 4 flavors of the
configuration file with WildFly since there are so
many different deployment scenarios. But this is still not enough. We need to be able to
tweak it at any point. The
jboss/wildfly image is not an exception here.
Following the Docker recreate — do not modify principle we do change the
configuration by creating a new image (in most cases). This allows us to reuse
the images (consider the
jboss/wildfly image itself).