# Can not upgrade 7.11.1 -\> 7.15.0 (docker-compose. dev.env)
**URL:** https://discuss.elastic.co/t/can-not-upgrade-7-11-1-7-15-0-docker-compose-dev-env/286676
**Category:** Elasticsearch
**Tags:** docker
**Created:** [October 14, 2021, 5:54am UTC](https://discuss.elastic.co/t/can-not-upgrade-7-11-1-7-15-0-docker-compose-dev-env/286676 "2021-10-14T05:54:25Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@zpsx](https://discuss.elastic.co/u/zpsx)
#### Post date: [October 14, 2021, 5:54am UTC](https://discuss.elastic.co/t/can-not-upgrade-7-11-1-7-15-0-docker-compose-dev-env/286676/1 "2021-10-14T05:54:25Z")
I am currently using the elastic stack in my development environment.
I'm using a single elastic stack system with docker compose.
The version used is 7.11.1.
I found out that 7.15.0 was released recently.
Change only the version in docker-compose.yml
command was executed. as below
docker-compose down
I did docker-compose up,
The version remains the same.
I wonder if there is another way.
I wonder why the upgrade is not working.
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [October 14, 2021, 7:14am UTC](https://discuss.elastic.co/t/can-not-upgrade-7-11-1-7-15-0-docker-compose-dev-env/286676/2 "2021-10-14T07:14:23Z")
Welcome!
This should not happen.
Stupid question but did you save your docket-compose file?
How do you know that the cluster was not upgraded?
Is there any other Elasticsearch instance running?
---
### Author:  [@zpsx](https://discuss.elastic.co/u/zpsx)
#### Post date: [October 14, 2021, 7:31am UTC](https://discuss.elastic.co/t/can-not-upgrade-7-11-1-7-15-0-docker-compose-dev-env/286676/3 "2021-10-14T07:31:50Z")
yea I did save
and check version by curl
result is
"name" : "dda9c6cf47d5",
"cluster\_name" : "docker-cluster",
"version" : {
"number" : "7.11.1",
---
### Author:  [@heikis](https://discuss.elastic.co/u/heikis)
#### Post date: [October 14, 2021, 8:01am UTC](https://discuss.elastic.co/t/can-not-upgrade-7-11-1-7-15-0-docker-compose-dev-env/286676/4 "2021-10-14T08:01:14Z")
Check if you have actually pulled the 7.15 image with "docker image ls".
If not then try "docker image pull [docker.elastic.co/elasticsearch/elasticsearch:7.15.0](http://docker.elastic.co/elasticsearch/elasticsearch:7.15.0)"
---
### Author:  [@zpsx](https://discuss.elastic.co/u/zpsx)
#### Post date: [October 14, 2021, 8:20am UTC](https://discuss.elastic.co/t/can-not-upgrade-7-11-1-7-15-0-docker-compose-dev-env/286676/5 "2021-10-14T08:20:47Z")
haha
oh I already did that...
OTL
docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
[docker.elastic.co/elasticsearch/elasticsearch](http://docker.elastic.co/elasticsearch/elasticsearch) 7.15.0 53ecd52afaa0 4 weeks ago 812MB
[docker.elastic.co/logstash/logstash](http://docker.elastic.co/logstash/logstash) 7.15.0 e5418407bc4d 4 weeks ago 977MB
[docker.elastic.co/kibana/kibana](http://docker.elastic.co/kibana/kibana) 7.15.0 4334c025a5e0 4 weeks ago 1.14GB
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [October 14, 2021, 12:51pm UTC](https://discuss.elastic.co/t/can-not-upgrade-7-11-1-7-15-0-docker-compose-dev-env/286676/6 "2021-10-14T12:51:38Z")
Could you run:
```auto
docker-compose down
```
And then when it's down, run
```auto
curl localhost:9200/
```
---
### Author:  [@zpsx](https://discuss.elastic.co/u/zpsx)
#### Post date: [October 15, 2021, 12:54am UTC](https://discuss.elastic.co/t/can-not-upgrade-7-11-1-7-15-0-docker-compose-dev-env/286676/7 "2021-10-15T00:54:44Z")
oh well done
It was a shameful mistake.
Thanks to everyone who gave advice
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 12, 2021, 12:55am UTC](https://discuss.elastic.co/t/can-not-upgrade-7-11-1-7-15-0-docker-compose-dev-env/286676/8 "2021-11-12T00:55:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.