# 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:** 1\
**Showing post:** 6

<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%).

---

_[View the full topic](https://meta.discourse.org/t/docker-system-is-not-a-docker-command-unable-to-run-launcher-cleanup/65783)._