21 days ago
Hello,
I'm experiencing a persistent build failure on my Railway project that appears to be related to an internal build infrastructure issue.
Project Details:
- Project ID: 661d3fbe-f710-414d-a381-d0be37c168db
- Environment: production
- Service: mialiko-api
Failed Deployment:
- Deployment ID: 585deaf4-8feb-4707-8eb0-6fb61c8df2d3
- Repository: leonard-shayo/mialiko-api
- Branch: master
- Commit: 16a2d332b50fdd2d8ca4dc986754ed85fea3b0fe
Steps Taken:
- Attempted redeploy (new deployment ID: 6037c537-57ce-401e-8ced-3d7a311398c3)
Error:
Build Failed: build daemon returned an error < failed to solve: secret app not found >
Failure Stage: BUILD_IMAGE
Issue Description: The build fails during the Maven package installation step with a BuildKit internal error related to secret mount resolution. This is not caused by application code or configuration changes. The triggering commit only pinned mysql-connector-j to version 9.1.0 and added a Hikari connection-init-sql property in application.properties—neither affects the build process.
The service is a standard Java 22 / Maven application correctly auto-detected by Railpack with no custom build configuration.
Please investigate the build daemon and secret resolution issue on your infrastructure side.
Thank you, Leonard
1 Replies
Status changed to Awaiting Railway Response Railway • 21 days ago
Status changed to Open Railway • 19 days ago
11 days ago
This does not look Maven-specific to me. failed to solve: secret app not found usually means the Railpack build plan is referencing a build secret named app, but BuildKit was not given that secret.
I would check the repo for railpack.json, railpack-plan.json, or any generated plan/config that has "secrets": ["app"] or "secrets": ["App"]. If that value is only needed at runtime, remove it from the build secrets list. If it is needed during build, make sure Railway has a variable with the exact same name/case and that it is available to the build.
The useful thing to send Railway support is the generated Railpack plan section that contains secrets, plus the failed deployment id. The dependency change is probably just the commit that caused a rebuild, not the root cause.