Docker is an open source project with a high-level API that provides software containers to run processes in isolation. Packaging an app in a container that can run on any Linux server (as well as on OS X and Windows) helps developers focus on developing the app instead of server setups and other DevOps operations.
Chapter 1, Installing Docker, takes you through the Docker installation process to start a container.
Chapter 2, Exploring Docker, gives you an insight into how Docker works and the terminology used and introduces public images.
Chapter 3, Creating Our First PaaS Image, shows you how to create your own custom Docker image that will be a part of your PaaS.
Chapter 4, Giving Containers Data and Parameters, teaches you about the data storing alternatives available and how to pass parameters to your PaaS containers.
Chapter 5, Connecting Containers, shows you how to manually connect containers in order to form a complete platform, and introduces two tools that give you more control over multicontainer platforms.
Chapter 6, Reverse Proxy Requests, explains the problem and provides a solution to having multiple containers on the same host, where more than one host should be reachable on the same port.
Chapter 7, Deployment on Our PaaS, takes you through the process of deploying code to your PaaS. Here, you learn how to create your own mini-Heroku with Dokku.
Chapter 8, What's Next?, introduces a few projects that are in their early stages and look promising for the future of a Docker based PaaS.
This book is intended for those who want to learn how to take full advantage of separating services into module containers and connecting them to form a complete platform. You may have, perhaps, heard of Docker but never installed or used it; or, you may have installed it and run a full stack container, not separating services in module containers that connect. In either case, this book will give you all the insights and knowledge required to run your own PaaS.
In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "After some dependent images are downloaded, we should be able to see our running container when we execute docker.ps."
A block of code is set as follows:
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Hello</title> </head> <body> <h1>First edit!</h1> </body> </html>
Any command-line input or output is written as follows:
curl -sSL https://get.docker.com/ubuntu/ | sudo sh
New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Open the Finder window and navigate to your Applications folder; locate boot2docker and double-click on it."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of.
To send us general feedback, simply e-mail <[email protected]>, and mention the book's title in the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files from your account at http://www.packtpub.com for all the Packt Publishing books you have purchased. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you could report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website or added to any list of existing errata under the Errata section of that title.
To view the previously submitted errata, go to https://www.packtpub.com/books/content/support and enter the name of the book in the search field. The required information will appear under the Errata section.
Piracy of copyrighted material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors and our ability to bring you valuable content.
If you have a problem with any aspect of this book, you can contact us at <[email protected]>, and we will do our best to address the problem.