On Thu, Aug 12, 2010 at 10:29, Daniel Lezcano dlezc...@fr.ibm.com wrote:
Answering to your question, if you do lxc.network.type=macvlan, the
network stack will be private to your container.
Hi Daniel,
not sure I understand your response: with macvlan option, you cannot
access to the container
On 08/19/2010 02:33 PM, Sebastien Douche wrote:
On Thu, Aug 12, 2010 at 10:29, Daniel Lezcanodlezc...@fr.ibm.com wrote:
Answering to your question, if you do lxc.network.type=macvlan, the
network stack will be private to your container.
Hi Daniel,
not sure I understand your
On 08/12/2010 01:05 AM, Nirmal Guhan wrote:
On Wed, Aug 11, 2010 at 11:05 AM, Serge Hallyn
serge.hal...@canonical.com wrote:
Quoting Nirmal Guhan (vavat...@gmail.com):
On Wed, Aug 11, 2010 at 5:06 AM, Serge Hallyn
serge.hal...@canonical.com wrote:
Quoting Nirmal Guhan (vavat...@gmail.com):
Hi,
Want to know if port numbers are virtualized for containers or do the
containers and host share the port space ? Please let me know.
--Nirmal
--
This SF.net email is sponsored by
Make an app they can't live
Quoting Nirmal Guhan (vavat...@gmail.com):
Hi,
Want to know if port numbers are virtualized for containers or do the
containers and host share the port space ? Please let me know.
Wrong layer. If the container shares a network namespace with the
host, then it shares its networking. If it
On Wed, Aug 11, 2010 at 11:05 AM, Serge Hallyn
serge.hal...@canonical.com wrote:
Quoting Nirmal Guhan (vavat...@gmail.com):
On Wed, Aug 11, 2010 at 5:06 AM, Serge Hallyn
serge.hal...@canonical.com wrote:
Quoting Nirmal Guhan (vavat...@gmail.com):
Hi,
Want to know if port numbers are
