# Docker Compose Issues on AWS

**URL:** <https://forums.docker.com/t/docker-compose-issues-on-aws/143703>\
**Category:** General\
**Tags:** aws\
**Created:** [September 12, 2024, 4:38am UTC](https://forums.docker.com/t/docker-compose-issues-on-aws/143703 "2024-09-12T04:38:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thegreatbritain](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/thegreatbritain/32/38998_2.png) [@thegreatbritain](https://forums.docker.com/u/thegreatbritain)\
**Post date:** [September 12, 2024, 4:38am UTC](https://forums.docker.com/t/docker-compose-issues-on-aws/143703/1 "2024-09-12T04:38:26Z")

</div>

### The stack is suppose to stop, bring down and bring up and containers run in AWS EC2

### I am running 20.10.24 docker on AWS EC2, when I updated the docker, I could no longer locate my containers. I then downgraded back to 20.10.24 and still cannot locate my containers. When I run the following docker commands below, there are issues, such as storage issues and or it just doesn’t work/load properly. The containers are unable to run currently.

Are there new docker commands that we should be using instead to get the containers (4) to run?

Docker-compose commands:  
cd website/docker  
DOCKER\_BUILDKIT=1 docker-compose -f docker-compose-local.yml build (instead of local its beta)  
docker-compose -f docker-compose-local.yml up -d (instead of local its beta)  
docker-compose -f docker-compose-local.yml down (instead of local its beta)

---

<div class="post-metadata">

**Author:** ![rimelek](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/rimelek/32/41602_2.png) [@rimelek](https://forums.docker.com/u/rimelek)\
**Post date:** [September 12, 2024, 10:29pm UTC](https://forums.docker.com/t/docker-compose-issues-on-aws/143703/2 "2024-09-12T22:29:32Z")

</div>

“there are issues”

what exactly?

Upgrade can change storage driver which means data is stored in a different directory. Or it changes the docker data root. If it is not changed back when you downgrade the version, it will not solve the problem.

---

<div class="post-metadata">

**Author:** ![thegreatbritain](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/thegreatbritain/32/38998_2.png) [@thegreatbritain](https://forums.docker.com/u/thegreatbritain)\
**Post date:** [September 13, 2024, 4:41am UTC](https://forums.docker.com/t/docker-compose-issues-on-aws/143703/3 "2024-09-13T04:41:43Z")

</div>

So the containers are not being restored and therefore are not running. As a result, everytime DOCKER\_BUILDKIT=1 docker-compose -f docker-compose-local.yml build is ran, it requires even more space. So not sure what to do to get the containers to run again?

---

<div class="post-metadata">

**Author:** ![rimelek](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/rimelek/32/41602_2.png) [@rimelek](https://forums.docker.com/u/rimelek)\
**Post date:** [September 13, 2024, 11:30am UTC](https://forums.docker.com/t/docker-compose-issues-on-aws/143703/4 "2024-09-13T11:30:05Z")

</div>

First check the output of this command:

```auto
ls -l /var/lib/docker

```

and share it.