Re: Finalize Docker Invoke JSON format

Hi Alan, Thanks for the feedback. I have sent a pull request (created from a separate branch) which has the docker test fixes. With this the unit tests works out of the box. Right now docker activity test has inspect image.(implementation support many including create/start etc). I will be adding

Re: Finalize Docker Invoke JSON format

On 24-Jun-16 06:58, Nadeesh Dilanga wrote: Hi all, Hello Yes, SSL issue also went away. When I point cert path in docker-java it picks it up without any concern. Great. At the moment the cert-path in TestDockerCommands is hard-coded with values like "/Users/Nadeesh/Documents/docker/" .

Re: Finalize Docker Invoke JSON format

Hi all, Yes, SSL issue also went away. When I point cert path in docker-java it picks it up without any concern. I sent a pull request with latest code changes. And now the RemoteClient(Utility client for docker commands) supports - Inspect an Image - Search Images - List all Containers - Create

Re: Finalize Docker Invoke JSON format

On 23 June 2016 at 07:17, Nadeesh Dilanga wrote: > With the help of maven dependency tree, was able to rule out all possible > places that packs in old jacksons. And since you mentioned about 2.7.4, I > only added following and was able to get rid of above error. So that

Re: Finalize Docker Invoke JSON format

Hi, With the help of maven dependency tree, was able to rule out all possible places that packs in old jacksons. And since you mentioned about 2.7.4, I only added following and was able to get rid of above error. So that means docker-java can work with 2.7.4. I am in the process of doing code

Re: Finalize Docker Invoke JSON format

On 18-Jun-16 08:12, Nadeesh Dilanga wrote: Hi Alan, Hi Stian, Please refer my latest commit @ https://github.com/NadeeshDilanga/incubator-taverna-common-activities/commits/docker/taverna-docker-activity where I have implemented reading a injected configuration. Can you please review this and

Re: Finalize Docker Invoke JSON format

Hi, I also sent a pull request https://github.com/apache/incubator-taverna-common-activities/pull/5 with my current four commits. On Tue, Jun 21, 2016 at 3:21 AM, Nadeesh Dilanga wrote: > Hi Stain, Hi Alan, > Can you please review the code with my latest commit @ >

Re: Finalize Docker Invoke JSON format

Hi Stain, Hi Alan, Can you please review the code with my latest commit @ https://github.com/NadeeshDilanga/incubator-taverna-common-activities/commits/docker where I came up with a Configuration Manager and also implemented "Configurable". I would like to add a unit test case for this by

Re: Finalize Docker Invoke JSON format

Hi all, one more thing to add. Create container is the most heavy API call(payload/parameter size). But how about things like start/stop/search/info/delete/ like methods. Should be think on accepting them as as activity plugin configs ? On Sat, Jun 18, 2016 at 3:12 AM, Nadeesh Dilanga

Re: Finalize Docker Invoke JSON format

Hi Alan, Hi Stian, Please refer my latest commit @ https://github.com/NadeeshDilanga/incubator-taverna-common-activities/commits/docker/taverna-docker-activity where I have implemented reading a injected configuration. Can you please review this and let me know what I am missing here. But one

Re: Finalize Docker Invoke JSON format

On 17-Jun-16 05:32, Nadeesh Dilanga wrote: Still got stuck further on the SSL issue[1]. May be something to do with my setup. So I also implemented invoking simple HTTP(without SSL) in additional to HTTP SSL. Meanwhile I already started getting configuration thru that spring inject-able

Re: Finalize Docker Invoke JSON format

It is the container host and I am invoking the remote API. Will do more troubleshooting and get back. On Wed, Jun 15, 2016 at 7:05 AM, Alan Williams wrote: > On 15-Jun-16 09:02, Nadeesh Dilanga wrote: > >> Hi Alan, >> Thank you very much for the pointer. I went through

Re: Finalize Docker Invoke JSON format

On 15-Jun-16 09:02, Nadeesh Dilanga wrote: Hi Alan, Thank you very much for the pointer. I went through and understood how works. 1. Implement docker factory class to return an activity configuration. 2. Accept the configuration in the DockerActivity constructor. Please correct me if I missed

Re: Finalize Docker Invoke JSON format

Hi Alan, Thank you very much for the pointer. I went through and understood how works. 1. Implement docker factory class to return an activity configuration. 2. Accept the configuration in the DockerActivity constructor. Please correct me if I missed something. Also I am working on the

Re: Finalize Docker Invoke JSON format

Hi Alan, Do you have an example link where we have used such Spring Configuration ? On Mon, Jun 13, 2016 at 9:28 AM, Alan Williams wrote: > On 10-Jun-16 02:49, Nadeesh Dilanga wrote: > >> Hi Stian, >> >> Following API can be used to attach to a remote Docker. Refer

Re: Finalize Docker Invoke JSON format

Hi Stian, Following API can be used to attach to a remote Docker. Refer "Attach to a container" for more details. POST /containers/(id or name)/attach Ok, it make sense to read it from some sort of a configuration instead from the input JSON for the activity plugin. Inside an activity plugin,

Re: Finalize Docker Invoke JSON format

Perhaps we need a configuration/preferences per Workbench/workflow about where to run the docker images. It's going to be different per user.. e.g. if you use Docker on a Mac then it will be some local IP address to the virtual machine - but then it's probably going to be the same for each

Re: Finalize Docker Invoke JSON format

Is it possible/easy to submit stdin input via the REST API? The API discusses if "One client attaches to STDIN" under the "Attach to a container" section. https://docs.docker.com/engine/reference/api/docker_remote_api_v1.23/#attach-to-a-container this uses HTTP 1.1 upgrade to a pure TCP

Re: Finalize Docker Invoke JSON format

Hi Alan, Can you please elaborate what you mean by " It is not sufficient to just start the container if it expects input data to be sent to stdin, or to be in specific locations." ? When starting a container using remote API, the only response we get is a HTTP status code along with a message

Re: Finalize Docker Invoke JSON format

On 04-Jun-16 05:10, Nadeesh Dilanga wrote: Hi all, I am starting this thread to discuss and finalize the docker commands we need to expose for client side(Taverna). Latest stable docker remote API is version 1.23[1]. And it has several APIs that can be useful. Yes. Where do you intend to run

Re: Finalize Docker Invoke JSON format

Hi Stian, New container for every execution means, we actually not start a container with a given name, but automatically generated name as you mentioned and just start container in every workflow node execution ? Can one workflow have more than one Docker invocation steps ? Yes, now it really

Re: Finalize Docker Invoke JSON format

Hi! I think we can assume that docker images are in the registry, although I know it's possible to specify alternate registries as well, which is useful for commercial entities. In could even be possible to store a custom docker image within the Taverna wfbundle zip, although it would make it

Finalize Docker Invoke JSON format

Hi all, I am starting this thread to discuss and finalize the docker commands we need to expose for client side(Taverna). Latest stable docker remote API is version 1.23[1]. And it has several APIs that can be useful. The original JIRA [2] mentioned about the JSON format to a docker run. I hope