Since both Docker and boot2docker are changing so rapidly, rather than describe the detailed steps here, I've provided an overview of the process so that you'll understand what's happening. This chapter will walk you through the installation process. The main difference is that our "docker" process is running inside a VM, rather than as a native service. If you've ever used a package like Postgres or MySql, it's exactly the same idea: you have a client tool that you use to issue commands to another server. So, the idea behind boot2docker is really quite clever: since we can't run Docker natively on Windows or a Mac, we install a bare-bones Linux VM that can run Docker, and then we communicate with it using a Docker client running on our host (i.e., the terminal on our main OS). For all intents and purposes, the VM is another computer running "inside" your computer - it has its own operating system, filesystem, and network that can piggyback on the resources of the host OS in an isolated environment. If you're unfamiliar with VMs, they let you run a "guest" operating system (like Linux) on your "host" operating system (like a Mac or Windows). To use it on a Mac or Windows, you must use a command-line tool called boot2docker that installs a Linux virtual machine (or "VM") on your system. Additional Resources Using boot2docker to run Docker on a Mac or WindowsÄocker's underlying containerization technology only works on Linux.
0 Comments
Leave a Reply. |