Persistent Build Infrastructure Error: "secret Internal not found"
sufillxman
FREEOP

16 days ago

Hi Railway Support Team,

I am facing a persistent build failure with my service secure-blessing. The build fails during the BUILD_IMAGE stage with the following error: Build Failed: build daemon returned an error < failed to solve: secret Internal not found >

Key Details:

  • Service Name: secure-blessing
  • Deployment ID (Latest):(Yahan apna latest failed deployment ID daal dena, jaise 5876751e...)
  • Error Context: The error occurs during the installation of apt packages (default-libmysqlclient-dev and default-mysql-client).
  • Observations: The exact same code and configuration built successfully at 05:38 UTC today. However, all subsequent deployments (15+ attempts) have failed with this identical infrastructure error, regardless of code changes.

I have already tried clearing the build cache, making empty commits, and triggering manual redeploys, but the "secret Internal" error persists. It seems to be a BuildKit/daemon issue on your end.

Please investigate the build daemon for this service and resolve the secrets resolution issue.

Thank you, Manknojiya Sufiyan

Solved$10 Bounty

1 Replies

Status changed to Open Railway 16 days ago


15 days ago

Do any of your environment variables contain a dot (.) in the name, for example something like Internal.Database.URL? If so, try renaming them to use underscores instead (e.g., Internal_Database_URL) and redeploy. Let us know if that resolves the build error.


Status changed to Awaiting User Response Railway 15 days ago


Railway
BOT

8 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 8 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...