I am getting the Your Docker installation is not working correctly issue after doing ./launcher rebuild app. The error is docker: failed to register layer: Error processing tar file(exit status 1): write /usr/lib/x86_64-linux-gnu/libx265.a: no space left on device. …I see one of the common tips on how to fix this is ./launcher cleanup, but before I do I’d like to check so it is safe to use, since I am getting: WARNING! This will remove all stopped containers. WARNING! This will remove all images without at least one container associated to them. Helps? Just want to make sure I don’t delete anything important here. docker ps -a [Screenshot 2024-06-04 at 14.52.08] docker images [Screenshot 2024-06-04 at 14.51.02]

It’s definitely the recommended option: [image]Manually update Discourse and Docker image to latest I’m running low on disk space If you are running low on disk space (check with df) try clearing up old images using: ./launcher cleanup apt-get autoclean apt-get autoremove Though if you want to make sure you have your site up and running before you press the button you can ./launcher start app first.

Running ./launcher start app gives the same error: docker: failed to register layer: Error processing tar file(exit status 1): write /usr/lib/x86_64-linux-gnu/libx265.a: no space left on device. See 'docker run --help'. Your Docker installation is not working correctly …so I still don’t know the answer to the question: is it safe to use ./launcher cleanup when the site is not up and running? From the screenshot under ‘docker images’ in the top post it seems there are a lot of older images, but don’t know how to target them specifically for deletion, and whether this would cause any troubles. df [Screenshot 2024-06-04 at 14.50.10]

[image] Osa Isacson: is it safe to use ./launcher cleanup when the site is not up and running? If the docker container is running, it won’t delete the container. If the container is not running, it’ll delete the container, but you can rebuild a new one with ./launcher rebuild app.

Thank you, but still not super clear to me - Docker is not my strong suit so I don’t know whether deleting and rebuilding a container would mess anything up on my site… Would it be safer to get the app up and running first by clearing out some selective space? Like this: First clear up some space by targeting a specific image to delete Then run ./launcher start app Once the app is up and running: ./launcher cleanup …not sure if this caution is needed. Perhaps just doing ./launcher cleanup straight up would work fine and not delete anything important even though my app is not running. But in case you think the above approach could be an option: do you know the command for targeting a specific image to delete (step 1 above)? See my options for which images to delete below. [Screenshot 2024-06-04 at 22.00.05]

What I would do is first delete a backup or two? That should give you enough space for things to function. If you run ./launcher start app then ./launcher cleanup will not delete your image that works, and your site will keep working while the cleanup progresses. If some somehow make a mistake and delete your image that does work, and you’ve upgraded recenlty, there’s a pretty good chance that you can just do a ./launcher rebuild app and be in good shape.

Do you know the command for just deleting a backup or two? Something like ./ launcher cleanup [id of image] perhaps?

I don’t believe ./launcher cleanup removes any backups, just containers that are not in use.

Did cd /var/discourse/shared/standalone/backups/default ls rm oldest-file tried ./launcher rebuild app …failed with memory issue as before did ./launcher cleanup Cleaned 4GB tried ./launcher rebuild app Got back failed with new errors. Did ./discourse-doctor, trying to figure out what’s up. …seems to have solved it? No clue why though. Would love to understand for next time. [image] bygg.boihop.co Mötesplatsen för idéburet byggande i Sverige

If you got a memory error on the rebuild then I’d add another GB of swap, though that’ll make your disk space issue tighter (It sounds like you’re on a small droplet with 25GB of RAM, which is just barely enough). I’d run a ./launcher cleanup before each rebuild, or maybe you just have a bunch of backups and should move them to S3 ([Configure an S3 compatible object storage provider for uploads](Configure an S3 compatible object storage provider for uploads --you can do just backups, you don’t have to do all of the assets as described there).

Your Docker installation is not working correctly - no space left on device - safe to use ./launcher cleanup?

Product Support Self-hosting

pfaffman (Jay Pfaffman) June 5, 2024, 3:37pm 9

cd /var/discourse/shared/standalone/backups/default
ls 
rm file-to-delete

Topic		Replies	Views
Docker: 'system' is not a docker command. Unable to run ./launcher cleanup Self-hosting	7	8166	July 10, 2017
Site Not Functioning After Attempted Upgrade Self-hosting	5	1241	December 9, 2019
Upgrading when space seems low: stop app, then cleanup, then rebuild app? Self-hosting server-resources	5	630	January 31, 2024
10-year self-hosted discourse admin asks: why not launcher cleanup as part of rebuild? Self-hosting	14	620	August 15, 2025
Stuck in a loop of freeing up space and filling it up again when rebuilding Self-hosting server-resources	30	4327	March 20, 2019

Your Docker installation is not working correctly - no space left on device - safe to use ./launcher cleanup?

Related topics