The discussion revolves around an issue with the ./launcher cleanup command in Docker, where users encounter the error docker: 'system' is not a docker command, indicating they are using an outdated Docker version. SMT reports low disk space and seeks ways to clean up, despite using Amazon S3 for backups. mpalmer notes that the older Docker version lacks modern features, and suggests the ./launcher should detect this and fall back to an older cleanup method. JagWaugh advises checking disk usage and backup retention, suggesting excess data from imports or restores might be the cause. Pad_Pors shares a similar situation with a 13GB forum on an 18GB instance, unable to access the app. Falco asks about Docker version and recommends using --skip-prereqs to bypass checks.
./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’.
Try freeing up space on the disk other ways.
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.
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…)
How to clean up the space meanwhile?
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.
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%).
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?
Are you running a recent Docker, version 17.x ?
You can add --skip-prereqs to ignore any checks too.