On Thu, Feb 12, 2015 at 1:19 AM, Ben <benoi...@gmail.com> wrote:
> Many thanks Ben!
>
> I was about to post my workaround I created yesterday to make it work, and I
> realize now (please correct me if I am wrong) that the ovs-docker script is
> doing what I found yesterday :
>
> pid=$(docker inspect -f '{{.State.Pid}}' $id) ## getting the PID of the
> container
> ln -s /proc/$pid/ns/net /var/run/netns/$pid ## creating a ln
> ip link add eth0 type veth peer name ovs-eth0 ## creating a veth peer
> ovs-vsctl add-port br ovs-eth0 ## adding one end of the peer to ovs
> ip link set eth0 netns $pid ## sending the second end to container namespace
Yes. That is all it does.> > Many thanks Ben! > > On 12/02/2015 1:26, Ben Pfaff wrote: > > On Wed, Feb 11, 2015 at 10:32:17AM +0100, Ben wrote: > > I am starting to work with Docker and saw an section at the end of this > article (http://www.opencloudblog.com/?p=66). > Basically I am creating some containers and want to use ovs for virtual > switching purpose. > > You should probably start from INSTALL.Docker.md in current OVS master. > > > > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
