# Upgrade from v2.0.0.beta10 +37 to 2.1.0.beta1 does fail

**URL:** https://meta.discourse.org/t/upgrade-from-v2-0-0-beta10-37-to-2-1-0-beta1-does-fail/89225
**Category:** Self-hosting
**Created:** [6 ביוני,‏ 2018,‏ 5:41am UTC](https://meta.discourse.org/t/upgrade-from-v2-0-0-beta10-37-to-2-1-0-beta1-does-fail/89225 "2018-06-06T05:41:57Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![GuidoD](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/guidod/32/292621_2.png) [@GuidoD](https://meta.discourse.org/u/GuidoD)
#### Post date: [8 ביוני,‏ 2018,‏ 5:18am UTC](https://meta.discourse.org/t/upgrade-from-v2-0-0-beta10-37-to-2-1-0-beta1-does-fail/89225/6 "2018-06-08T05:18:17Z")

</div>

One additional thing, I read in some of the beta release notes of 2.0 (I think it was beta 6 or 7) that it will automatically upgrade to postgres 10.  
But even though I always had installed every new beta I just noticed that our installation it is still on postgres 9.5 (psql (PostgreSQL) 9.5.12)  
I assume I will have to follow the instructions mentioned in the template of this [post](https://meta.discourse.org/t/docker-base-image-with-postgresql-10-released/84536) to get it on 10, right?

I also tracked the complete output in my last try into a file in order to check the output.  
I do see that the rebuild starts with a fatal:

```plaintext
root@marktplatz:/var/discourse# ./launcher rebuild app
fatal: ref HEAD is not a symbolic ref
Stopping old container
+ /usr/bin/docker stop -t 10 app
app
cd /pups && git pull && /pups/bin/pups --stdin
Already up-to-date.

```

I remember that I have seen the fatal already for quite some time but it still did upgrade the betas.  
I do see in the /var/discourse/.git directory a file called HEAD from last year  
-rw-r–r-- 1 root root 41 Oct 18 2017 HEAD

What will I have to do to remove the fatal at the beginning?

---

_[View the full topic](https://meta.discourse.org/t/upgrade-from-v2-0-0-beta10-37-to-2-1-0-beta1-does-fail/89225)._