[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=13042810#comment-13042810 ] 

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

Let me map these:

1-2: actually running docker instance is something we can initially document/provide links for. Next version we can look into having a way to easily run boot2docker/vagrant/etc. but I think there will be so many variations trying to keep up with it in the plugin is too early.
3: we will try detect the ip where we can, but because of the many combinations I think we will in addition on trying to autodetect also simply listen to a ~/.docker.cfg or similar that can be shared between scripts and tools (both in and outside eclipse). And in all cases it will possible to explicitly put an ip/hostname into the docker UI
4 same as 9 - will be made available from the image and container view as 'Add...' or 'Run...' action
5 that is what container view does
6 context menu/stop button in container view
7 that is what image view does
8 context menu/delete button in image view
9 see #4
10 Run in context menu. Should provide UI to map ports, links, volumes and console log will show the output ...possibly use terminal ui for it to provide input.
11/12 you mean disconnected terminal ? not sure it makes sense to have explicit in eclipse ui, but just allow to open/close the console log for a container.

13-16 is extremely specific to what the image is capable of doing so this is not covered by generic docker tooling. Also, do you expect the deployment to be incremental (thus requiring understanding/assume alot about the volume mappings) or be complete ones (thus just relying on management API being exposed)

17) context menu action
18) context menu action - I think we should put docker registry interactions in separate sub task.

19) I image "Docker build" as being a context menu action on DockerFile files in the project explorer.




> 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
>          Components: openshift, requirements
>            Reporter: Burr Sutter
>            Assignee: Xavier Coulon
>
> 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)