> For the complete documentation index, see [llms.txt](https://docs.trymito.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trymito.io/getting-started/installing-mito/installing-mito-in-a-docker-container.md).

# Installing Mito in a Docker Container

Step by step instructions for installing Mito with a Docker file.

## Before Installing Mito

Verify that the Docker image is using **Python 3.9** or greater and **JupyterLab 4.1** or greater.

## Installing Mito

Add the following command to your docker file:

```
RUN pip install --no-cache-dir mito
```

Then, after you launch this container, you can run a classic Jupyter Notebook or JupyterLab instance and create a mitosheet with the following standard instructions.

### Example

Here is a minimal example of a Dockerfile which you can use to build an image with Mito

```
# Use the official Jupyter minimal notebook as the base image
FROM quay.io/jupyter/minimal-notebook:latest

# Install Python packages
RUN pip install --no-cache-dir mito-ai mitosheet
```

### Best practices

It is a best practice to pin the version of Mito that you are installing in a Docker container, for example

```
RUN pip install --no-cache-dir mito-ai==0.1.52
```

{% content-ref url="/pages/-MSFWSHvT14R-vec2dxe" %}
[Creating a Mitosheet](/how-to/creating-a-mitosheet.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trymito.io/getting-started/installing-mito/installing-mito-in-a-docker-container.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.