> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/solutions/unable-to-start-pf9-kube-service-on-master-node.md).

# Unable to Start pf9-kube Service on Master Node

## Problem

* Unable to start **pf9-kube** service on the master node
* Below errors are reported in */var/log/pf9/pf9-kube/kube.log*

{% tabs %}
{% tab title="None" %}

```none
docker: Error response from daemon: devmapper: Thin Pool has 6844 free data blocks which is less than minimum required 6859 free data blocks. Create more free space in thin pool or use dm.min_free_space option to change behavior.See 'docker run --help'.
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - v3.6.0 and higher
* Docker

## Cause

There are not enough free data blocks on the node. This may be due to dead and/or exited containers still residing on the host.

## Resolution

1. Check the number of containers in dead or exited state.

{% tabs %}
{% tab title="None" %}

```none
# docker ps -a -q -f status=dead# docker ps -a -q -f status=exited
```

{% endtab %}
{% endtabs %}

2. Run the below command to clean up any containers matching dead or exited status:

{% tabs %}
{% tab title="None" %}

```none
# docker rm $(docker ps -a -f status=exited -q)# docker rm $(docker ps -a -f status=dead -q)
```

{% endtab %}
{% endtabs %}


---

# 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://platform9.com/kb/pmk/solutions/unable-to-start-pf9-kube-service-on-master-node.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.