[jbosstools-issues] [JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)

[Max Rydahl Andersen (JIRA)]

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

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

initial comment is that this jira is mixing up alot of things.

0,1,2,3:
Making sure docker is running is not something we will do - users will provide a ip to connect to; just like all other tools that uses docker do. If we already know the IP we don't need to run boot2docker, and it should in any way be configured/read from environment variables to fit best with other tools.

3:
Run As functionallity - this does not fit in the overall system afaics. Run As implies you have deployed something, which we can't on a docker instance before it is running. This usecase shuold be separated out and detailed since I as is now it would require a really custom workflow that would not handle many users need for docker being flexible. But lets outline it in separte jira.

5,6,7,9:
Basic docker operations (ps, rm,rmi, etc.) these should be part of JBDS-3256

8:
docker build uses whatever is in your dockerfile - wether it has a war or ear embedded is up to the user.




> Docker Tooling (Advanced Integration)
> -------------------------------------
>
>                 Key: JBDS-3258
>                 URL: https://issues.jboss.org/browse/JBDS-3258
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>            Reporter: Burr Sutter
>            Assignee: Max Rydahl Andersen
>
> Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear.  
> In addition to the basic integrations of pull, run, stop, commit and push 
> boot2docker init 
> boot2docker up
> boot2docker down
> boot2docker ip
> docker run -d 
> docker ps
> docker rm
> docker rmi
> docker build
> End-user steps:
> 0) assumes boot2docker has been dowloaded and installed
> 1) boot2docker init : required to to insure boot2docker-vm is properly initialized 
> 2) boot2docker up : starts the VirtualBox boot2docker-vm 
> 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability.
> 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously
> 5) docker ps : allows me to see all my currently running containers
> 6) docker rm : allows me to kill a currently running container
> 7) docker rmi : allows me to remove a local image
> 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded
> 9) docker run : this new created image
> The docker build scenario can be triggered via a Maven plugin
> The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install)
> We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn.  So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests.



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