Network of Docker in Deigo enviroment

[Harry Zhang]

Hi, 

I noticed the fatanstic demo of Docker in Diego posted on http://thenewstack.io/docker-on-diego-cloud-foundrys-new-elastic-runtime/ , and I found a statement like below:

It will run in a Warden container. Diego does not run Docker containers. It has an interface to run compatible images in Warden containers.

So I have two concerns of this approch:

 

1. Network configuration of this case

    We use our own network bridge and pipework in production container env, so I'm really interested in what's the network like in Docker+Warden+Diego world?

2. Limitations of running Docker inside Warden

    I really don't wanna change single line of my code inside the Docker, but is it possible in this "container in container" scenary? 

[James Bayer]

please see: https://docs.google.com/a/pivotal.io/document/d/12akzXK4yYU1Jf3YKIf3heDT5taN8qEHMGICJ8SAQxQw/edit#heading=h.gjdgxs

and let us know if you still have questions.

--
You received this message because you are subscribed to the Google Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/32bedb08-9f68-4db1-9102-1e615e9beb5d%40cloudfoundry.org.

To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+u...@cloudfoundry.org.

--

Thank you,

James Bayer

[James Bayer]

more inline now that i have more time...

On Tue, Oct 14, 2014 at 6:48 AM, James Bayer <jba...@pivotal.io> wrote:

please see: https://docs.google.com/a/pivotal.io/document/d/12akzXK4yYU1Jf3YKIf3heDT5taN8qEHMGICJ8SAQxQw/edit#heading=h.gjdgxs

and let us know if you still have questions.

On Mon, Oct 13, 2014 at 11:41 PM, Harry Zhang <res...@gmail.com> wrote:

Hi, 

I noticed the fatanstic demo of Docker in Diego posted on http://thenewstack.io/docker-on-diego-cloud-foundrys-new-elastic-runtime/ , and I found a statement like below:

It will run in a Warden container. Diego does not run Docker containers. It has an interface to run compatible images in Warden containers.

So I have two concerns of this approch:

 

1. Network configuration of this case

    We use our own network bridge and pipework in production container env, so I'm really interested in what's the network like in Docker+Warden+Diego world? 

in the first iteration we're only supporting a single inbound http port just like today's buildpack applications. the only difference between the apps will be one is a docker image reference and the other is a tgz blob that is the output of a buildpack staging process. both still run in warden containers. diego will not actually use the docker executable to run the docker image, but rather pull the docker image and the referenced layers from the referenced registry using docker libraries and once the full image is available on the diego cell, then setup the container, put the docker image inside of it and issue the start command with warden.

 

2. Limitations of running Docker inside Warden

    I really don't wanna change single line of my code inside the Docker, but is it possible in this "container in container" scenary?

if the only inbound port you receive is http, then there likely isn't any change. if you're relying on docker exe features like container linking, mounting volumes, etc then those docker images are likely not going to work as-is. you should look at the docker-boshrelease for docker images that need all of the docker exe features: https://github.com/cf-platform-eng/docker-boshrelease

 

--
You received this message because you are subscribed to the Google Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/32bedb08-9f68-4db1-9102-1e615e9beb5d%40cloudfoundry.org.

To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+u...@cloudfoundry.org.

--

Thank you,

James Bayer

[Harry Zhang]

Now I think I got the Docker idea in Diego: it's runtime support for Docker container! And the real value here is that developers can push anything they like by a Docker image and serve outside world thru Router. For example, push my MySQL Docker image to CF.