In our last post we introduced ourselves to CNI (if you haven’t read that yet, I suggest you start there) as we worked through a simple example of connecting a network namespace to a bridge. CNI managed both the creation of the bridge as well as connecting the namespace to the bridge using a VETH pair. In this post we’ll explore how to do this same thing but with a container created by Docker. As you’ll see, the process is largely the same. Let’s jump right in.
This post assumes that you followed the steps in the first post (Understanding CNI) and have a ‘cni’ directory (~/cni) that contains the CNI binaries. If you don’t have that – head back to the first post and follow the steps to download the pre-compiled CNI binaries. It also assumes that you have a default Docker installation. In my case, Im using Docker version 1.12.
The first thing we need to do is to create a Docker container. To do that we’ll run this command…
user@ubuntu-2:~/cni$ sudo docker run --name cnitest --net=none -d jonlangemak/web_server_1 835583cdf382520283c709b5a5ee866b9dccf4861672b95eccbc7b7688109b56 user@ubuntu-2:~/cni$
Notice that when we ran the command we told Docker to use a network of ‘none’. Continue reading
Take survey and enter to win one of three $300 Amazon Gift Cards.
The post On the ‘net: Net Neutrality Explained appeared first on 'net work.
Gabriele Di Piazza, VP of solutions, Telco NFV Group at VMware, shares his predictions for what will be generating the most buzz at MWC.
The idea of using cloud brains to simplify on-premises management holds a lot of promise for the future.
More than 101,000 attendees from 160 countries are expected at the conference.
The show is hosting three panels on these topics.
Ericsson probably won't be the only vendor to show off data center gear at MWC.