# New Version, how to handle it

**URL:** <https://community.datagerry.com/t/new-version-how-to-handle-it/69>\
**Category:** Community Support\
**Created:** [March 6, 2020, 1:51pm UTC](https://community.datagerry.com/t/new-version-how-to-handle-it/69 "2020-03-06T13:51:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![J.Limmer](https://avatars.discourse-cdn.com/v4/letter/j/a587f6/32.png) [@J.Limmer](https://community.datagerry.com/u/J.Limmer)\
**Post date:** [March 6, 2020, 1:51pm UTC](https://community.datagerry.com/t/new-version-how-to-handle-it/69/1 "2020-03-06T13:51:36Z")

</div>

If a new Version of DATAGERRY is released, what do we need to do to update our default docker-based installation? Without loosing data, for sure.

---

<div class="post-metadata">

**Author:** ![mbatz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/mbatz/32/5_2.png) [@mbatz](https://community.datagerry.com/u/mbatz)\
**Post date:** [March 6, 2020, 2:40pm UTC](https://community.datagerry.com/t/new-version-how-to-handle-it/69/2 "2020-03-06T14:40:01Z")

</div>

Hi @J.Limmer,

just pull the new version of the DATAGERRY Docker image, if you use the latest tag in your docker-compose.yml or switch to tag `1.1.0`. and restart the container. On the first start of the new version, an existing database will be migrated automatically to the new version.

---

<div class="post-metadata">

**Author:** ![J.Limmer](https://avatars.discourse-cdn.com/v4/letter/j/a587f6/32.png) [@J.Limmer](https://community.datagerry.com/u/J.Limmer)\
**Post date:** [March 9, 2020, 6:30am UTC](https://community.datagerry.com/t/new-version-how-to-handle-it/69/3 "2020-03-09T06:30:32Z")

</div>

Thanks. To be fair I don’t really know docker. So I tried running **docker pull nethinks/datagerry** which didn’t change anything so I read a little bit about it and came up with a working procedure.

To help other docker-noobs I will share what I did:

- Navigating to the folder where the docker-compose.yml had been saved
- Running **docker-compose pull**
- After successfully pulling the new image I ran **docker-compose up -d**

---

<div class="post-metadata">

**Author:** ![mbatz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/mbatz/32/5_2.png) [@mbatz](https://community.datagerry.com/u/mbatz)\
**Post date:** [March 9, 2020, 5:02pm UTC](https://community.datagerry.com/t/new-version-how-to-handle-it/69/4 "2020-03-09T17:02:49Z")

</div>

Thanks for sharing. We should improve our documentation with a better description of an update process.

---

<div class="post-metadata">

**Author:** ![adnan.smajic](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/adnan.smajic/32/754_2.png) [@adnan.smajic](https://community.datagerry.com/u/adnan.smajic)\
**Post date:** [June 20, 2023, 10:40am UTC](https://community.datagerry.com/t/new-version-how-to-handle-it/69/5 "2023-06-20T10:40:32Z")

</div>