<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 17, 2016 at 4:59 PM, John Doyle <span dir="ltr"><<a href="mailto:jdoyle@redhat.com" target="_blank">jdoyle@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Jun 17, 2016 at 6:37 AM, Heiko W.Rupp <<a href="mailto:hrupp@redhat.com">hrupp@redhat.com</a>> wrote:<br>
> Hey,<br>
><br>
> I was able to make some progress with Dockerizing Hawkular-services<br>
> More technical details below<br>
><br>
> As it is relatively hard (not impossible) to do stuff like adding a user<br>
> inside a (immutable) docker container or to edit standalone.xml to<br>
> enable the agent, we need to decide how we add the (default) user<br>
> to hawkular docker container and also if/how to enable the embedded<br>
> agent.<br>
><br>
> Also as we more understand hawkular-services as one package,<br>
> we should perhaps figure out if we really need the flexibility to<br>
> modify standalone.xml on the fly with all our snippets and templates<br>
> or if we create a 'hardcoded' one that can be used for the process<br>
> going forward.<br>
<br>
</span>Very few layered products have created their own dedicated<br>
standalone.xml. To be honest I don't understand the reluctance.<br>
Configuration changes in maintenance releases are rejected unless<br>
absolutely needed for security purposes, so breakage is very unlikely.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br>+1<br> </div><br></div></div></div>