# Can we stop DevKinsta from starting containers on host startup?

**URL:** https://community.kinsta.com/t/can-we-stop-devkinsta-from-starting-containers-on-host-startup/1550
**Category:** Application Support
**Created:** [June 13, 2022, 9:54pm UTC](https://community.kinsta.com/t/can-we-stop-devkinsta-from-starting-containers-on-host-startup/1550 "2022-06-13T21:54:39Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Ethan91](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/ethan91/32/791_2.png) [@Ethan91](https://community.kinsta.com/u/Ethan91)
#### Post date: [June 13, 2022, 9:54pm UTC](https://community.kinsta.com/t/can-we-stop-devkinsta-from-starting-containers-on-host-startup/1550/1 "2022-06-13T21:54:39Z")

</div>

Title. I only use DevKinsta for a subset of sites I work on and don’t need its containers to start on boot. Can this be disabled?

---

<div class="post-metadata">

### Author: ![Kevin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/kevin/32/808_2.png) [@Kevin](https://community.kinsta.com/u/Kevin)
#### Post date: [June 14, 2022, 4:38pm UTC](https://community.kinsta.com/t/can-we-stop-devkinsta-from-starting-containers-on-host-startup/1550/2 "2022-06-14T16:38:41Z")

</div>

Hi @Ethan91, thanks for reaching out. You will have to do this through Docker by changing the restart policy. You can do so with this command:

`docker update --restart=no devkinsta_nginx devkinsta_db devkinsta_adminer devkinsta_mailhog devkinsta_fpm`

The DevKinsta containers should now only start after you start DevKinsta. Please let us know if that doesn’t work!

---

<div class="post-metadata">

### Author: ![Ethan91](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/ethan91/32/791_2.png) [@Ethan91](https://community.kinsta.com/u/Ethan91)
#### Post date: [June 21, 2022, 6:23pm UTC](https://community.kinsta.com/t/can-we-stop-devkinsta-from-starting-containers-on-host-startup/1550/3 "2022-06-21T18:23:56Z")

</div>

That worked @Kevin - thanks so much!

---

<div class="post-metadata">

### Author: ![c-hartmann](https://avatars.discourse-cdn.com/v4/letter/c/c2a13f/32.png) [@c-hartmann](https://community.kinsta.com/u/c-hartmann)
#### Post date: [June 5, 2024, 7:21am UTC](https://community.kinsta.com/t/can-we-stop-devkinsta-from-starting-containers-on-host-startup/1550/4 "2024-06-05T07:21:48Z")

</div>

this info seems to be outdated. at least for (Ubuntu) Linux

i had to “sudo” the command:

```auto
sudo docker update --restart=no devkinsta_nginx devkinsta_db devkinsta_adminer devkinsta_mailhog devkinsta_fpm

```

and:

```auto
sudo docker kill devkinsta_fpm && docker kill devkinsta_nginx && docker kill devkinsta_adminer && docker kill devkinsta_db && docker kill devkinsta_mailhog

```

---

<div class="post-metadata">

### Author: ![sami\_c](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/sami_c/32/3908_2.png) [@sami\_c](https://community.kinsta.com/u/sami_c)
#### Post date: [September 17, 2024, 8:39am UTC](https://community.kinsta.com/t/can-we-stop-devkinsta-from-starting-containers-on-host-startup/1550/5 "2024-09-17T08:39:59Z")

</div>

> [@Kevin](#):
>
> docker update --restart=no devkinsta\_nginx devkinsta\_db devkinsta\_adminer devkinsta\_mailhog devkinsta\_fpm

Add this to stop them is they are up :  
`docker stop devkinsta_nginx devkinsta_db devkinsta_adminer devkinsta_mailhog devkinsta_fpm`