AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Vagrant docker3/11/2023 If we end up adopting a service like one of these, we may end up dropping Chef all together, but we're not ready to let go of those reigns yet. One thing to mention is that we have yet to dive into the Docker specific hosts such as AWS ECS, dotCloud, or Tutum. Chef would be used in a much more limited capacity, only managing configuration on a system level not an application level. My thought is that we would use Chef to manage the various Docker hosts that we deploy containers to and use the Dockerfile with Docker Compose to manage the actual app container configuration. Chef is great for machine level provisioning. It doesn't seem quite right to completely abandon Chef yet, since Docker still needs a machine to run the Docker host. Our team has extensive experience using Chef to manage infrastructure at scale. My opinion may change after gaining more real world experience with Docker in production, but the mindset that I'm coming from is that in production our Docker hosts will be managed via Chef. Let me tell you why I think you shouldn't use Boot2Docker or Kitematic locally, but first a rabbit trail. Running either of these two packages looks appealing to get Docker up locally very quickly (and you should use one of these packages if you're just trying out Docker), but thinking big picture and how we plan to use Docker in production, it seems that we should take a different approach locally. If you read the Docker OS X installation docs, you see there are two options for running Docker on Mac OS X, Boot2Docker or Kitematic. Unfortunately you can't run Docker natively on OS X, Docker needs to run in a Virtual Machine with an operating system such as Linux. Running a Docker hostįor background, we are specifically an all Mac OS X shop at ActiveLAMP, so I'll be speaking from this context. However, I am leaning toward taking an unconventional approach to installing Docker locally, not mentioned in the Docker documentation. I don't intend to walk you through how to install Docker, you can find step-by-step installation instructions based on your OS in the Docker documentation. There are several ways to go about setting up Docker locally. It's definitely worth checking out, and using that as a base to build FROM for your custom images. I want to give a shout out to the folks that maintain the Drupal Docker image in the Docker Registry. This post is focused on hashing out a Docker workflow with Vagrant, less about Drupal itself. By the end of this post, we'll have Drupal running in a container, using Docker. In this post, we will venture into setting up docker locally, in the same repeatable way from developer to developer, by using Vagrant. To gain background of what I want to accomplish with docker, checkout my previous post hashing out a docker workflow. This post is part 2 in a series of Docker posts hashing out a new docker workflow for our team.
0 Comments
Read More
Leave a Reply. |