[
https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin...
]
Rafal Korytkowski commented on TEIID-5372:
------------------------------------------
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:
1) As a base docker image with vdbs, drivers and config added as part of a docker build in
Dockerfile.
2) As a docker instance with vdbs, drivers and config read from a mounted volume using
wildfly deployment scanner or loaded other ways into a running instance.
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?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)