# Your local changes to the following files would be overwritten by checkout

**URL:** <https://forum.ansible.com/t/your-local-changes-to-the-following-files-would-be-overwritten-by-checkout/20669>\
**Category:** Ansible Developer\
**Tags:** ansible-devel\
**Created:** [February 24, 2016, 7:06pm UTC](https://forum.ansible.com/t/your-local-changes-to-the-following-files-would-be-overwritten-by-checkout/20669 "2016-02-24T19:06:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [February 24, 2016, 7:06pm UTC](https://forum.ansible.com/t/your-local-changes-to-the-following-files-would-be-overwritten-by-checkout/20669/1 "2016-02-24T19:06:43Z")

</div>

The usual cause to this happening is running a `git pull` from inside of lib/ansible/modules/core

The cause to the mention of `-dirty` is that “Submodules are now regarded as dirty if they have any modified files or untracked files”

In your case it seems to indicate that you have changes to cloud/docker/docker\_image.py

I do not have access to your full workflow, but I am guessing you are performing `git checkout` or `git pull` or other such things in the submodules. If you do these types of things, expect to have to reset and update your submodules.