|
literally, buildx_buildkit_coolify-railpack0_state takes up 55.94GB after use for not too long. I've noticed the same issue on a second coolify instace, storage is running out fast. I tried running a manual clean up but that doesn't do shit, perhaps the clean up service doesn't track |
Replies: 1 comment 1 reply
|
you need to run docker buildx --builder coolify-railpack prune whilst its running, there was a bug with the initial railpack release where the host did not know about the new buildx builder so couldn't prune it. if the above command doesn't work, remove and delete both the builder and its volume, future builds should recreate the builder such that it can then be pruned on the host i would also advise manually creating the builder on the host such that you can set limits, as coolify does not set any (make sure you do this using the user that is used for docker) so after removing and deleting the builder run something like |
you need to run docker buildx --builder coolify-railpack prune whilst its running, there was a bug with the initial railpack release where the host did not know about the new buildx builder so couldn't prune it.
if the above command doesn't work, remove and delete both the builder and its volume, future builds should recreate the builder such that it can then be pruned on the host
i would also advise manually creating the builder on the host such that you can set limits, as coolify does not set any (make sure you do this using the user that is used for docker)
so after removing and deleting the builder run something like