> 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/error-initializing-docker-graphdriver-expected-integer.md).

# Error Initializing Docker: "graphdriver: expected integer"

## Problem

Docker fails to start with the following error message.

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

```none
Error starting daemon: error initializing graphdriver: expected integer
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - All Versions
* Docker
* CentOS
* LVM

## Cause

The node may have been re-used from a previous Kubernetes cluster for which the Docker volume group (LVM) was not recreated.

## Resolution

**Warning**: The following will erase any data associated with the logical volume(s) contained within the volume group. If you are uncertain about this operation, it may be recommended to perform a backup following the guide provided under the [Additional Information](#h_1ca04858-7406-4d82-aa90-e5459c8ae92a) section.

1. Remove any logical volumes associated with the volume group.

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

```none
# lvremove [vg-name]/[lv-name]
```

{% endtab %}
{% endtabs %}

2. Remove the volume group.

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

```none
# vgremove [vg-name]
```

{% endtab %}
{% endtabs %}

3. Re-create the volume group following the instructions outlined in the [Platform9 Managed Kubernetes CentOS prerequisites](https://docs.platform9.com/support/preparing-centos-7-system-running-containers/).

## Additional Information

[LVM: Taking a Backup Using Snapshots](http://tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.html)


---

# 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 dynamically 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/error-initializing-docker-graphdriver-expected-integer.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 `build a script that syncs our docs to a CMS` 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.