Great, I could work on a page describing different deployment models some time next week and put it under Teiid 4 Ways.

I'd expect docker instances to be persistently mutable. I'd envision wildfly with docker to be used two-fold:

Enhance docker support ---------------------- Key: TEIID-5372 URL: https://issues.jboss.org/browse/TEIID-5372 Project: Teiid Issue Type: Enhancement Reporter: Rafal Korytkowski Assignee: Rafal Korytkowski Priority: Optional Currently there's limited support for docker in Teiid, which can be enabled by adding -Ddocker=true to the build command. The generated image is based on CentOS and running standalone on the Wildfly server. Latest builds are pushed to https://hub.docker.com/r/jboss/teiid/, but versions are not tagged automatically with releases. Development with Docker is not supported. Proposed changes: 1. Produce docker image based on Alpine, which is better suited for microservices, in addition to CentOS. 2. Automatically tag versions in Docker when doing releases. 3. Support development by providing a docker-compose file with the possibility to start server in a debug mode and enabled auto-redeployment of code changes. 4. Optionally provide a Docker image for building code using maven in Docker. Having Docker as the only prerequisite is convenient for CI environments and makes the build environment agnostic. [~shawkins], [~rareddy], thoughts?