# Docker: 'system' is not a docker command. Unable to run ./launcher cleanup

**URL:** https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783
**Category:** Self-hosting
**Created:** [July 7, 2017, 4:41am UTC](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783 "2017-07-07T04:41:39Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![SMT](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@SMT](https://meta.discourse.org/u/SMT)
#### Post date: [July 7, 2017, 4:41am UTC](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783/1 "2017-07-07T04:41:39Z")

</div>

./launcher cleanup  
flag provided but not defined: --format  
See ‘/usr/bin/docker info --help’.  
You have less than 5GB of free space on the disk. You will need more space to continue

Would you like to attempt to recover space by cleaning docker images and containers in the system?(y/N)y  
docker: ‘system’ is not a docker command.  
See ‘docker --help’.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [July 7, 2017, 4:42am UTC](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783/2 "2017-07-07T04:42:17Z")

</div>

Try freeing up space on the disk other ways.

---

<div class="post-metadata">

### Author: ![SMT](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@SMT](https://meta.discourse.org/u/SMT)
#### Post date: [July 7, 2017, 4:43am UTC](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783/3 "2017-07-07T04:43:33Z")

</div>

Thanks for the quick reply. What are the other ways to clean up? I m even using amazon s3 for images. I don’t know why it is taking so much of space.

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [July 7, 2017, 4:46am UTC](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783/4 "2017-07-07T04:46:07Z")

</div>

You’re running an older version of Docker, that doesn’t come with all the fancy stuff that’s in newer versions. @Falco, we probably need to detect that in `./launcher` and either bail out with an error, or revert to an older method of diskspace cleanup. (I also find it kind of amusing that you need to delete data in order to run cleanup…)

---

<div class="post-metadata">

### Author: ![SMT](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@SMT](https://meta.discourse.org/u/SMT)
#### Post date: [July 7, 2017, 4:57am UTC](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783/5 "2017-07-07T04:57:02Z")

</div>

How to clean up the space meanwhile?

---

<div class="post-metadata">

### Author: ![JagWaugh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagwaugh/32/69335_2.png) [@JagWaugh](https://meta.discourse.org/u/JagWaugh)
#### Post date: [July 7, 2017, 5:07am UTC](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783/6 "2017-07-07T05:07:13Z")

</div>

How much space have you got? (df -h)  
How many backups are you retaining on your droplet? (move them to S3 if you haven’t already done so)  
Is your content from an import or a restore? (You may be carrying excess baggage from that. See [here](https://meta.discourse.org/t/disk-space-usage-by-postgres/61137/4).

I’m guessing that your instance is a bit behind, the rebuild updated ./launcher itself (You got the “new” You have less than launcher message), then failed because docker is out of date (iirc @Falco stated that the new cleanup will work even if the disk is at 100%).

---

<div class="post-metadata">

### Author: ![Pad\_Pors](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pad_pors/32/52016_2.png) [@Pad\_Pors](https://meta.discourse.org/u/Pad_Pors)
#### Post date: [July 10, 2017, 7:42pm UTC](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783/7 "2017-07-10T19:42:29Z")

</div>

We got the same error, it’s a 13G forum on a 18G instance.

I can’t enter app either, we’ve also moved the backups to S3. is there anything else I can remove so that we can rebuild the app?

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [July 10, 2017, 7:59pm UTC](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783/8 "2017-07-10T19:59:21Z")

</div>

Are you running a recent Docker, version 17.x ?

You can add `--skip-prereqs` to ignore any checks too.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [June 8, 2024, 12:44pm UTC](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783/9 "2024-06-08T12:44:27Z")

</div>

This topic was automatically closed after 2528 days. New replies are no longer allowed.
