Docker for PHP Developers (NomadPHP)
•
3 recomendaciones•823 vistas
Thanks to tools like vagrant, puppet/chef, and Platform as a Service services like Heroku, developers are extremely used to being able to spin up a development environment that is the same every time. What if we could go a step further and make sure our development environment is not only using the same software, but 100% configured and set up like production. Docker will let us do that, and so much more. We’ll look at what Docker is, why you should look into using it, and all of the features that developers can take advantage of.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Docker for PHP Developers (NomadPHP)
Similar a Docker for PHP Developers (NomadPHP) (20)
Más de Chris Tankersley
Más de Chris Tankersley (20)
Último
Último (20)
Docker for PHP Developers (NomadPHP)
- 2. Who Am I • PHP Programmer for over 11 years • Sysadmin/DevOps for around 9 years • Using Linux for more than 15 years • hJps://github.com/dragonmantank • Author of “Docker for Developers” • Reigning, Defending, Undisputed PHP MTG Champion of the World NomadPHP EU April 2016 2
- 5. What is it from a technical standpoint? • Docker is a wrapper around Containers • Docker Engine is the packaging porXon that builds and runs the containers • Docker Hub allows you to publish images for others to use • Docker Machine is a bare-metal provisioning tool • Docker Swarm is an load-balancing deployment tool • Docker Compose is a mulX-container build system NomadPHP EU April 2016 5
- 7. Normal Bare-Metal Server NomadPHP EU April 2016 7 CPU RAM HD Network OperaXng System nginx PHP DB
- 8. Virtual Machines NomadPHP EU April 2016 8 CPU RAM HD Network OperaXng System nginx PHP DB OperaXng System nginx PHP DB OperaXng System Hypervisor
- 9. Containers NomadPHP EU April 2016 9 CPU RAM HD Network OperaXng System nginx nginx PHP DB PHP DB
- 10. Docker can use many different containers • Since 0.9.0 it supports: • LXC (Linux Containers) – Started with LXC when it was released • OpenVZ • Systemd-nspawn • libvert-sandbox • Qemu/kvm • BSD Jails • Solaris Zones • chroot NomadPHP EU April 2016 10
- 11. Runs on *nix and Windows Hyper-V • No naXve container drivers for OSX* • Amazon has ElasXc Container Service, and Microsok Azure has Azure Container Service NomadPHP EU April 2016 11
- 12. Sorry OSX Users • Docker support is officially maintained through Docker Toolbox NomadPHP EU April 2016 12
- 13. Docker Toolbox also is for Windows NomadPHP EU April 2016 13
- 15. Running a container • `docker run` will run a container • This will not restart an exisXng container, just create a new one • docker run [opXons] IMAGE [command] [arguments] • [opXons ]modify the docker process for this container • IMAGE is the image to use • [command] is the command to run inside the container • [arguments] are arguments for the command NomadPHP EU April 2016 15
- 16. Running a simple shell NomadPHP EU April 2016 16
- 17. Running a simple shell NomadPHP EU April 2016 17
- 18. Running a simple shell NomadPHP EU April 2016 18
- 27. Some Notes • All three containers are 100% self contained • Docker containers share common ancestors, but keep their own files • `docker run` parameters: • --rm – Destroy a container once it exits • -d – Run in the background (daemon mode) • -i – Run in interacXve mode • --name – Give the container a name • -p [local port]:[container port] – Forward the local port to the container port NomadPHP EU April 2016 27
- 29. Modifying a running container • `docker exec` can run a command inside of an exisXng container • Use Volumes to share data NomadPHP EU April 2016 29
- 30. Persistent Data with Volumes • You can designate a volume with -v • Volumes can be shared amongst containers • Volumes can mount data from the host system NomadPHP EU April 2016 30
- 31. Mounting from the host machine NomadPHP EU April 2016 31
- 32. Mounting from the host machine NomadPHP EU April 2016 32
- 33. Mounting from the host machine NomadPHP EU April 2016 33
- 34. Mounting from the host machine NomadPHP EU April 2016 34
- 35. Mounting from the host machine NomadPHP EU April 2016 35
- 36. Mounting from the host isn’t perfect • The container now has a window into your host machine • Permissions can get screwy if you are modifying in the container • Most things it creates will be root by default, and you probably aren’t root on the host machine • Host-mounted volumes are not portable at all • Docker Toolbox’s VM only allows mounXng from within your home directory NomadPHP EU April 2016 36
- 37. Container Data Volumes • Uses a small container that does nothing but stores data • Have our app containers use the data volume to store data • Use ‘editor containers’ to go in and modify data when needed NomadPHP EU April 2016 37
- 46. Why not run SSH inside of the container? • Well, you can… • Docker is designed for one command per container • If you need to modify data, then you need to change your setup • If you have to run SSH, then you need a way to run SSH and your command NomadPHP EU April 2016 46
- 47. Why go through the hassle? • Data volumes are portable • Data volumes are safer • Separates the app containers from data • ProducXon can use a data volume, dev can use a host volume • Our app containers stay small NomadPHP EU April 2016 47
- 49. Docker Links • Allows containers to ‘see’ each other over the network • Each container thinks the other one is just another machine • Containers all have an internal network address, so we don’t need to expose everything through the host • Currently only works if all the containers are on one machine, Docker 1.10 should fix that NomadPHP EU April 2016 49
- 50. More Traditional Setup NomadPHP EU April 2016 50 INTARWEBS Nginx PHP-FPM Data Volume Port 9000 Editor
- 57. More Notes! • We can now rebuild secXons of the app as needed • We can restart nginx without impacXng PHP • We can extend much easier • Linked containers will not update if they are stopped/started • If we upgrade PHP, we have to destroy/create the web_server container again NomadPHP EU April 2016 57
- 58. Creating your own Images NomadPHP EU April 2016 58
- 59. Dockerfile • Dockerfile is the configuraXon steps for an image • Can be created from scratch, or based on another image • Allows you to add files, create default volumes, ports, etc • Can be used privately or pushed to Docker Hub NomadPHP EU April 2016 59
- 61. Build it docker build -t tag_name ./ • This runs through the Dockerfile and generates the image • We can now use the tag name to run the image NomadPHP EU April 2016 61
- 63. Inspect a container docker inspect [opXons] CONTAINER_NAME • Returns a JSON string with data about the container • Can also query • docker inspect -f “{{ .NetworkSe{ngs.IPAddres }}” web_server • Really handy for scripXng out things like reverse proxies NomadPHP EU April 2016 63
- 64. Work with images • docker pull IMAGE – Pulls down an image before using • docker images – Lists all the images that are downloaded • docker rmi IMAGE – Deletes an image if it’s not being used NomadPHP EU April 2016 64
- 66. What is Docker Machine? • A provisioning tool that is used to set up a box with Docker • Used in Docker Toolbox to create the VM • Supports: • EC2 • Azure • Digital Ocean • Hyper-V • OpenStack • Virtualbox • VMWare NomadPHP EU April 2016 66
- 67. Why use it? • Makes it very easy to spin up new boxes • Docker Machine handles all of the dirty stuff for you • Docker Toolbox users are already using it • Integrates with Docker Swarm • It is not necessarily portable NomadPHP EU April 2016 67
- 69. What is Docker Swarm? • Cluster management tool developed by Docker • Looks like a machine running docker, but is actually many machines NomadPHP EU April 2016 69
- 71. What is Docker Compose? • MulX-container orchestraXon • A single config file holds all of your container info • Works with Docker Swarm and a few other tools, like Rancher NomadPHP EU April 2016 71
- 74. I can’t answer this for you NomadPHP EU April 2016 74 ¯_(ツ)_/¯
- 76. Each situation is different • You will probably build something custom, using exisXng tools • Do you use data volumes? • Do you just package the enXre compiled app? • Does it need to be distributed? • Is it going on Swarm, or Amazon ECS? NomadPHP EU April 2016 76
- 77. Things to consider • Docker Compose will only deploy an app to one server • Docker Swarm is preJy low-level and bare-bones • Volumes on Swarm cannot be shared across hosts • Host mounXng is 99.99999% of the Xme not what you want to do NomadPHP EU April 2016 77
- 78. Rancher is a good start • Provides a nice GUI to manage everything • Allows volume sharing and networking across hosts • Works with docker-compose.yml files • These files can be supplemented with environment variables NomadPHP EU April 2016 78