If you’ve followed along in my other network posts about bridge and the rest of the default networks, you may have noticed that I keep spinning up CentOS containers. This is well and good for demos and instructional purposes but you might have also noticed that they don’t really do anything. I mean they exist, but that isn’t why you run things in your environment. You don’t have a bunch of server OSes spun up doing nothing, right? RIGHT?
Well, we hope not anyway. Ideally your server actually does something like hosts an app, database, or webserver. In this post we are going to explore some aspects of bridge networking and get a little more into the underpinnings of Docker. And in order do that, hey we need a container that actually does something! Continue reading
As with our previous post on bridge, the intent here is to explore the remaining standard (mostly non-swarm) network configurations. Those configurations are host, none, and the newer MACVLAN.
Unlike bridge these are non-default configurations which means you must manually specify the network somewhere. In our case we are just going to explicitly list the network when we run the container. We will also explore the configuration elements that we looked at earlier. Continue reading
If you have been under a rock (like I was for a while!), Docker is a container technology and containers are very cool. Containers sparked my interest in the same way that virtualization did the first time I saw it. I really regret not getting into it sooner but better late than never. Seriously if you haven’t played with containers at all try it on a local system, VM, or use this really nifty site http://training.play-with-docker.com/