developers' network - quick start guides to bootstrap examples

(Perfect for people with a short attention span, needing to get work done!)


Highly similar to the concept of VM images created in a development environment and released to a production server, Docker allows you to create an environment for running software which can then be moved around without spending time worrying about inconsistencies between server environments (e.g. Ubuntu, CentOS, OSX, or Windows).

As we've covered in many other entries here on OSCC, we use Ansible heavily, and it works great in conjunction with Docker.

The six primary points to know about Docker are: 1)

  1. Everything starts with a Dockerfile.
  2. When you build the Dockerfile, you create the Image.
  3. With the image, you redistribute it using the Registry.
  4. You use the Image to run a Container.
  5. Containers are immutable, persistent storage is handled by Volumes.
  6. Docker resides in it's own Networks space that sits on top of the host operating system's space for extended capabilities:
    • Linking containers to each other
    • Linking to the host machine
    • Linking to public port(s) on public IP address(es).


There are several fundamentals of Docker, that have been split up into separate pages for readability:

FIXME: Clustering, Linking, Networks, Volumes.


Getting Started

More in-depth examples are explored in the "Run-time" section, but for now, let's try some simple examples, including the "Hello World" example that you probably already ran when testing your installation:



See also


External links