[
https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5372:
---------------------------------------
Teiid/JDV usage of docker images splits into several directions:
* Teiid-komodo generated images -
https://github.com/teiid/teiid-komodo/tree/2b2b0626c6eee570d9ba7bacfbd4cc...
This has been considered the forward looking work, but is obviously not what you are
looking for from a Teiid developer perspective.
* The underlying s2i build -
https://github.com/rareddy/teiid-openshift-demo/ shows
creating/deploying an image similar to what teiid-komodo is doing
* The teiid community image - which as you note is not really useful in and of itself.
Some of the limitations are also discussed on TEIID-5131
* The JDV product docker/openshift images - which are somewhat difficult to configure due
to config substitution approach taken by EAP
We need to decide from a community perspective if there's a value in still promoting
an image that is based upon the full WildFly integration. If so then a lot of what you
are looking to do makes sense. If not, then we need to work on documenting / expanding
the s2i build - for example accommodating multiple vdbs.
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)