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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBDS-3256:
-------------------------------------------

This is not what I consider basic docker tooling - this is appserver *specific* integration which for being possible needs to have someone produce these docker images. [~burrsutter] are you expecting the tools team products these ?

btw. we can do *all* of the above as long as the server inside the docker image is a standard jboss server and SSH is open to execute commands - so need to be more specific on what is expected here besides that.

For me basic docker features are those that just work with docker and does not assume any specifics about what is inside the docker image.

That means browsing images, run them and connect to them via  terminal.


> 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
>            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)