<commit_before>---
post_title: Using Mesos Containerizers
nav_title: Mesos Containerizers
menu_order: 3.5
---

Containerizers allow you to run tasks in containers. Running tasks in containers offers a number of benefits, including the ability to isolate tasks from one another and control task resources programmatically.

DC/OS supports the Mesos containerizer types [Mesos unified containerizer](http://mesos.apache.org/documentation/latest/containerizer/#Mesos) and [Docker containerizer](http://mesos.apache.org/documentation/latest/containerizer/#Docker).

# Mesos Unified Containerizer

The [Mesos unified containerizer](http://mesos.apache.org/documentation/latest/container-image) extends the Mesos containerizer to support provisioning [Docker](https://docker.com/) and [AppC](https://github.com/appc/spec) container images. This means that you can use both the Mesos containerizer and other container image types in DC/OS. While other containerizers still play well with DC/OS, the Mesos unified containerizer does not depend upon other container technologies and can therefore take advantage of more Mesos features.

The Mesos unified containerizer offers the following advantages:

* **Removes your dependency on the Docker daemon**: With previous versions of Docker, if the Docker daemon was not responsive, a restart to the daemon caused all containers to stop on the host. In addition, Docker must be installed on each of your agent nodes in order to use the Docker containerizer. This means that in order to use the Docker containerizer you need to upgrade Docker on the agent nodes each time a new version of Docker comes out.
* The Mesos unified containerizer is more stable and allows deployment at scale.
* The Mesos unified containerizer offers features not available in the Docker containerizer, such as GPU and CNI support.
* The Mesos unified containerizer allows you to take advantage of continuing innovation within both the Mesos and DC/OS, including features such as IP per container, strict container isolation and more.

**Note:** This new Mesos unified containerizer functionality is in the experimental phase. We encourage [feedback from the DC/OS community](https://dcos.io/community/).
<commit_msg>changed unified --> universal<commit_after>---
post_title: Using Mesos Containerizers
nav_title: Mesos Containerizers
menu_order: 3.5
---

Containerizers allow you to run tasks in containers. Running tasks in containers offers a number of benefits, including the ability to isolate tasks from one another and control task resources programmatically.

DC/OS supports the Mesos containerizer types [Mesos universal containerizer](http://mesos.apache.org/documentation/latest/containerizer/#Mesos) and [Docker containerizer](http://mesos.apache.org/documentation/latest/containerizer/#Docker).

# Mesos Universal Containerizer

The [Mesos universal containerizer](http://mesos.apache.org/documentation/latest/container-image) extends the Mesos containerizer to support provisioning [Docker](https://docker.com/) and [AppC](https://github.com/appc/spec) container images. This means that you can use both the Mesos containerizer and other container image types in DC/OS. While other containerizers still play well with DC/OS, the Mesos universal containerizer does not depend upon other container technologies and can therefore take advantage of more Mesos features.

The Mesos universal containerizer offers the following advantages:

* **Removes your dependency on the Docker daemon**: With previous versions of Docker, if the Docker daemon was not responsive, a restart to the daemon caused all containers to stop on the host. In addition, Docker must be installed on each of your agent nodes in order to use the Docker containerizer. This means that in order to use the Docker containerizer you need to upgrade Docker on the agent nodes each time a new version of Docker comes out.
* The Mesos universal containerizer is more stable and allows deployment at scale.
* The Mesos universal containerizer offers features not available in the Docker containerizer, such as GPU and CNI support.
* The Mesos universal containerizer allows you to take advantage of continuing innovation within both the Mesos and DC/OS, including features such as IP per container, strict container isolation and more.

**Note:** This new Mesos universal containerizer functionality is in the experimental phase. We encourage [feedback from the DC/OS community](https://dcos.io/community/).

{'fraction_non_alphanumeric': 0.056691863050244554, 'fraction_numerical': 0.0008892841262783459, 'mean_word_length': 5.196969696969697, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 4, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2331067', 'n_tokens_mistral': 1068, 'n_tokens_neox': 1020, 'n_words': 568}