muammereroglu opened a new pull request, #4575: URL: https://github.com/apache/activemq-artemis/pull/4575
**Issue**: After creating the artemis docker image using the official docker scripts, it is not possible to map a user supplied broker.xml using a volume mapping, before running the container at least once. Some questions related to this issue on stackoverflow: * https://stackoverflow.com/questions/75493917/how-to-customize-the-broker-xml-file-in-the-standard-apache-activemq-artemis-doc * https://stackoverflow.com/questions/71149959/how-to-provide-a-custom-broker-xml-to-activemq-artemis-broker-instance * https://stackoverflow.com/questions/76071388/how-can-i-replace-the-broker-xml-in-activemq-artemis-with-a-customized-broker-xm This very small patch solves the problem by introducing an **etc-override** folder. If an outside folder is mapped as volume to **/var/lib/artemis-instance/etc-override**, its contents will be copied to **etc** folder after instance creation. Therefore, the image will always start with user-supplied configuration, eg. custom broker.xml / artemis.profile files. This change does not modify the use case of mapping the whole instance folder. If the instance folder is mapped as volume, it is sufficient to place an **etc-override** folder inside the mapped folder, its contents will again be copied over **etc** folder. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
