github.com/vieux/docker@v0.6.3-0.20161004191708-e097c2a938c7/docs/userguide/intro.md (about)

     1  <!--[metadata]>
     2  +++
     3  title = "Introduction"
     4  description = "Introduction to user guide"
     5  keywords = ["docker, introduction, documentation, about, technology, docker.io, user, guide, user's, manual, platform, framework, home,  intro"]
     6  identifier = "engine_guide_intro"
     7  [menu.main]
     8  parent="engine_guide"
     9  +++
    10  <![end-metadata]-->
    11  
    12  # Engine user guide
    13  
    14  This guide takes you through the fundamentals of using Docker Engine and
    15  integrating it into your environment. You'll learn how to use Engine to:
    16  
    17  * Dockerize your applications.
    18  * Run your own containers.
    19  * Build Docker images.
    20  * Share your Docker images with others.
    21  * And a whole lot more!
    22  
    23  This guide is broken into major sections that take you through learning the basics of Docker Engine and the other Docker products that support it.
    24  
    25  ## Dockerizing applications: A "Hello world"
    26  
    27  *How do I run applications inside containers?*
    28  
    29  Docker Engine offers a containerization platform to power your applications. To
    30  learn how to Dockerize applications and run them:
    31  
    32  Go to [Dockerizing Applications](../tutorials/dockerizing.md).
    33  
    34  
    35  ## Working with containers
    36  
    37  *How do I manage my containers?*
    38  
    39  Once you get a grip on running your applications in Docker containers, you'll learn how to manage those containers. To find out
    40  about how to inspect, monitor and manage containers:
    41  
    42  Go to [Working with Containers](../tutorials/usingdocker.md).
    43  
    44  ## Working with Docker images
    45  
    46  *How can I access, share and build my own images?*
    47  
    48  Once you've learnt how to use Docker it's time to take the next step and
    49  learn how to build your own application images with Docker.
    50  
    51  Go to [Working with Docker Images](../tutorials/dockerimages.md).
    52  
    53  ## Networking containers
    54  
    55  Until now we've seen how to build individual applications inside Docker
    56  containers. Now learn how to build whole application stacks with Docker
    57  networking.
    58  
    59  Go to [Networking Containers](../tutorials/networkingcontainers.md).
    60  
    61  ## Managing data in containers
    62  
    63  Now we know how to link Docker containers together the next step is
    64  learning how to manage data, volumes and mounts inside our containers.
    65  
    66  Go to [Managing Data in Containers](../tutorials/dockervolumes.md).
    67  
    68  ## Managing metadata (labels) for Docker objects
    69  
    70  Labels are a mechanism for applying metadata to Docker objects, including:
    71  
    72  - Images
    73  - Containers
    74  - Local daemons
    75  - Volumes
    76  - Networks
    77  - Swarm nodes
    78  - Swarm services
    79  
    80  
    81  You can use labels to organize your images, record licensing information, annotate
    82  relationships between containers, volumes, and networks, or in any way that makes
    83  sense for your business or application.
    84  
    85  Go to [Managing Docker object labels](labels-custom-metadata.md).
    86  
    87  ## Docker products that complement Engine
    88  
    89  Often, one powerful technology spawns many other inventions that make that easier to get to, easier to use, and more powerful.  These spawned things share one common characteristic: they augment the central technology. The following Docker products expand on the core Docker Engine functions.
    90  
    91  ### Docker Hub
    92  
    93  Docker Hub is the central hub for Docker. It hosts public Docker images
    94  and provides services to help you build and manage your Docker
    95  environment. To learn more:
    96  
    97  Go to [Using Docker Hub](https://docs.docker.com/docker-hub/).
    98  
    99  ### Docker Machine
   100  
   101  Docker Machine helps you get Docker Engines up and running quickly. Machine
   102  can set up hosts for Docker Engines on your computer, on cloud providers,
   103  and/or in your data center, and then configure your Docker client to securely
   104  talk to them.
   105  
   106  Go to [Docker Machine user guide](https://docs.docker.com/machine/).
   107  
   108  ### Docker Compose
   109  
   110  Docker Compose allows you to define an application's components -- their containers,
   111  configuration, links and volumes -- in a single file. Then a single command
   112  will set everything up and start your application running.
   113  
   114  Go to [Docker Compose user guide](https://docs.docker.com/compose/).
   115  
   116  
   117  ### Docker Swarm
   118  
   119  Docker Swarm pools several Docker Engines together and exposes them as a single
   120  virtual Docker Engine. It serves the standard Docker API, so any tool that already
   121  works with Docker can now transparently scale up to multiple hosts.
   122  
   123  Go to [Docker Swarm user guide](https://docs.docker.com/swarm/).
   124  
   125  ## Getting help
   126  
   127  * [Docker homepage](https://www.docker.com/)
   128  * [Docker Hub](https://hub.docker.com)
   129  * [Docker blog](https://blog.docker.com/)
   130  * [Docker documentation](https://docs.docker.com/)
   131  * [Docker Getting Started Guide](../getstarted/index.md)
   132  * [Docker code on GitHub](https://github.com/docker/docker)
   133  * [Docker mailing
   134    list](https://groups.google.com/forum/#!forum/docker-user)
   135  * Docker on IRC: irc.freenode.net and channel #docker
   136  * [Docker on Twitter](https://twitter.com/docker)
   137  * Get [Docker help](https://stackoverflow.com/search?q=docker) on
   138    StackOverflow