Skip to content
Discussion options

You must be logged in to vote

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

docker buildx create \
  --name coolify-railpack \
  --driver docker…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@Heracraft
Comment options

Answer selected by Heracraft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants