[jbosstools-issues] [JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)

[Arun Gupta (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029453#comment-13029453 ] 

Arun Gupta commented on JBDS-3256:
----------------------------------

Here is some basic Docker tooling that would be helpful:

- Configure Docker Registries (public or private)
- Search images that on the configured registry
- Specify the name of an image that need to run the container. The image is downloaded, and possibly cached, if does not already exist.
- Like Servers tab at the bottom, it would be useful to have a Docker tab or provide a single UI to interact with everything Docker
- Orchestration of multiple Docker containers. For example, WildFly running in one container and MySQL in another one. Tooling can provide plumbing to make that happen.

[~maxandersen] Docker images already exist and defined at: http://www.jboss.org/docker/. As [~burrsutter] explained, app server-specific integration would be very useful, and much desirable by JBoss Tools.


> JBoss specific Docker Tooling (Basic Integration)
> -------------------------------------------------
>
>                 Key: JBDS-3256
>                 URL: https://issues.jboss.org/browse/JBDS-3256
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: openshift
>            Reporter: Burr Sutter
>            Assignee: Andre Dietisheim
>
> Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers.
> Expected end-user flow 1:
> 0) Installation - assumes boot2docker pre-installed on the end-user's machine
> 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag.
> 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location.
> 3) I start (docker run) the image which auto-starts the embedded app server
> 4) I can then deploy my .war or .ear to the running app server
> 5) I can restart the running app server in debug mode and run the debugger
> 6) I can undeploy and redeploy my .war or .ear 
> 7) I can stop/restart the running, embedded app server
> 8) I can then commit (docker commit)
> 9) then I can publish my changes (docker push)



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)