Introducing Docker to your Team

Over the course of several months I have had the opportunity to introduce the use of docker within development teams as an alternative approach for developing with Sitecore. Developing with Sitecore on Docker requires a bit of a mind shift from your normal way of working with Sitecore. But if offers many benefits like the ability to stand up a fully scaled instance of Sitecore in seconds rather than hours. This blog provides a introduction to docker and getting started developing with Sitecore on Docker.

What is Docker

Docker is a platform that enables you to develop, ship, and run applications as containers. The Docker Daemon process (or engine) runs on your host OS which manages images and containers.

The Command Line Interface (CLI) communicates with the docker daemon via rest API.

Containers vs VMs

Containers are an abstraction at the app layer that packages code and dependencies together. Multiple containers can run on the same machine and share the OS kernel with other containers, each running as isolated processes.

  • take up less space.
  • more portable and efficient.
  • require fewer VMs and Operating systems.
  • reduce cost as fewer licenses are required.
  • start in seconds.
  • are ephemeral – treated like cattle in your DevOps service model.

VMs are an abstraction of physical hardware turning one server into many servers. The hypervisor allows multiple VMs to run on a single machine.

  • includes a full copy of an operating system, the application, necessary binaries and libraries – are much larger in size.
  • VMs can also be slow to boot.
  • start in minutes
  • tend to hang around longer – treated more like pets in your DevOps service model.

By combining Containers and VMs in your infrastructure provide a great deal of flexibility in deploying and managing your application.

Sitecore Docker Repo

The Sitecore Docker Repo contains docker files for a plethora of Sitecore versions and their variants including: JSS, SXA, SPE. Also necessary scripts, tools and supporting documentation to help you build Sitecore Docker images and ultimately run a containerized instance of Sitecore.

dockerfiletocontainerLets backup for those of you that may not be familiar with some of these terms:

  • Dockerfile – is a text document that contains all the commands you would normally execute manually in order to build a Docker image.
    Docker can build images automatically by reading the instructions from a Dockerfile.
  • Docker Images – are the basis of containers. An Image is an ordered collection of root filesystem changes and the corresponding execution parameters for use within a container runtime. An image typically contains a union of layered filesystems stacked on top of each other. An image does not have state and it never changes.
  • Docker Container– is a runtime instance of a docker image.

Thanks to the hardwork and dedication to the individuals in our community that contribute to the Sitecore Docker repo. Which is continually evolving.

Continue reading

Monitoring Sitecore Containers

The ability to monitor your Sitecore instances is essential. Knowing your application is available and performing in production as expected is critical. To be proactive and respond to changes in performance as opposed to reactive after an incident has occurred, you need a continuous overview of the state of the application and the underlying infrastructure. This involves gathering metrics like CPU, memory usage, and storage consumption as well as any application-related metrics. However, when monitoring a containerized Sitecore instance we cannot apply our usual methods and tools to provide us with all the data we need. In this post, I will show you some of the native tools to help you monitor Sitecore containers.

Docker stats

The docker stats command display a live stream (updated every second) of running containers resource usage statistics docker stats:

dockerstats

  • CPU % – the percentage of the host’s CPU the container is using.
  • PRIV WORKING SET – refers to the total physical memory (RAM) used by the process.
  • NET I/O – the amount of data the container has sent and received over its network interface.
  • BLOCK I/O – the amount of data the container has read to and written from block devices on the host.

Continue reading

Tips for managing Sitecore containers

In this post, I will show you some useful commands and tips for managing your Sitecore containers, images and other docker resources that get created when standing up your containers. The Docker documentation is awesome but it is fairly extensive so I’ll cover some useful commands you should be familiar with.

PS> docker container ls – lists running containers by default, you need to use -a flag to list all containers not just running containers. You can use -f flag to filter containers.

PS> docker container ls -f “name=93x*”

dockercontainerslsfilter

If you want to see the most recently created use -l flag.

Continue reading

How to move Sitecore container images to an Azure Registry

If you have built your Sitecore container images and they reside locally and you want to share them with your team the recommended approach is a private registry and there are a few services available. However, Azure Container Registry (ACR) allows you to store docker images in repositories and can take advantage of the azure pipelines to automatically rebuild these images when they need to be updated. In this post, I will show you how to push your local images to a private ACR. This also works if you need to move your images from one private registry to another.

Shore crane loading containers in freight ship

Continue reading

Running Windows and Linux Containers Simultaneously

If you are running Sitecore in a container then you’ve most likely switched Docker desktop to Windows container mode. But what if you want to run a Linux container simultaneously? For example, you might want to fire up, JMeter and Grafana on Linux containers. It turns out this is possible in your local development environment and is fairly straightforward.

Crane lifting up container in yard

Continue reading

docker-compose up is music to one’s Sitecore ear!

Don’t worry this is not another post about running Sitecore in a container! No this is a post about getting the Sitecore HabitatHome demo solution up and running quickly and I mean quickly without too much effort. I just happen to use docker in the process. HabitatHome is a solution built using SXA on Sitecore XP following Helix principles. It is extremely useful if you need to showcase SXA capabilities to an existing or a potential new customer.

This is where my good friend Andy Uzick found himself a few weeks ago but had already started down the path of standing up the SXA HabitatHome demo on a temporary Azure PAAS instance not using docker. I thought with docker surely this would be much easier.

habitathomedemo

Continue reading