Railpack changes discovery strategy, leading to: failed to solve: mount options is too long

Is there any way to fix this myself or is Railpack just broken now?

@iloveitaly would have more context on what has changed.

Does appear to align with the timing of the two most recent commits on the railpack repo. My last successful build was ~17 hours ago, my first (failed) build didn't happen until ~12 hours ago. Are railpack versions in Railway in line with what is in the repo?

Off the top of my head, I think we do pull the latest version

This commit seems more suspect: https://github.com/railwayapp/railpack/commit/1c82cf3#diff-27ff8308c04317ea0cfad402a8a9e8c00a0a36bf908a7fadaacae56cb9fc171e

@therobotcarlson the railpack build that is used is tied to the latest release, not the latest commit. We haven't released anything in a couple days so if it worked earlier a couple days ago it should work now.

I have a feeling setting RAILPACK_DISABLE_CACHES=* would fix the issue

this definitely something we need to fix in the system though.

Thank you for the response. I should have dug more deeply into my own code instead of railpack.

At some point during the last 17 hours I added the offending folder .bun/install/cache to the repo in question despite it being in the .gitignore -> I did not even consider it a possibility that this folder had been pushed to the repo.

ahh interesting. Glad you figured out the issue!