# Why is docker-compose not working anymore with Umbrel 1.0?

**URL:** <https://community.umbrel.com/t/why-is-docker-compose-not-working-anymore-with-umbrel-1-0/15756>\
**Category:** Support and Troubleshooting\
**Created:** [March 22, 2024, 1:22pm UTC](https://community.umbrel.com/t/why-is-docker-compose-not-working-anymore-with-umbrel-1-0/15756 "2024-03-22T13:22:57Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![mayank](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/mayank/32/26_2.png) [@mayank](https://community.umbrel.com/u/mayank)\
**Post date:** [March 23, 2024, 12:22pm UTC](https://community.umbrel.com/t/why-is-docker-compose-not-working-anymore-with-umbrel-1-0/15756/6 "2024-03-23T12:22:33Z")

</div>

Totally get your frustration, folks! Apologies for the confusion.

To clarify, we’ve transitioned to a much more robust architecture. If you’d like to start/stop apps via command line, you can do the following:

Stop an app:

```auto
umbreld client apps.stop.mutate --appId <app-id>

```

Example:

```auto
umbreld client apps.stop.mutate --appId bitcoin

```

And start it with:

```auto
umbreld client apps.restart.mutate --appId <app-id>

```

---

_[View the full topic](https://community.umbrel.com/t/why-is-docker-compose-not-working-anymore-with-umbrel-1-0/15756)._