Skip to content

Railway Deployment #936f1d fix: remove git clone stage in actors#4

Open
railway-app[bot] wants to merge 2 commits intomainfrom
railway/fix-deploy-936f1d
Open

Railway Deployment #936f1d fix: remove git clone stage in actors#4
railway-app[bot] wants to merge 2 commits intomainfrom
railway/fix-deploy-936f1d

Conversation

@railway-app
Copy link
Copy Markdown

@railway-app railway-app bot commented Mar 20, 2026

Problem

The actors service fails to build because the Dockerfile's repo stage clones the repository via git to resolve submodule-backed workspace dependencies (iso-kv, iso-signatures, iso-ucan), but Railway cannot initialize git submodules. The actors/package.json uses workspace: references pointing to iso-repo/packages/*, an empty submodule directory, causing bun to fail resolution entirely.

Solution

Replaced the multi-stage Dockerfile with a single builder stage that uses Railway's built-in COPY . /project instead of cloning. Pinned iso-kv, iso-signatures, and iso-ucan to their last published npm versions (matching the last successful deployment) in actors/package.json, and removed the iso-repo/packages/* workspace entry from the root package.json.

Changes

  • Modified actors.Dockerfile
  • Modified actors/package.json
  • Modified package.json

Context

  • Deployment: #936f1d
  • Failed commit: 514f2a2

Generated by Railway

@zicklag zicklag force-pushed the main branch 2 times, most recently from dc62eff to 526cc7a Compare March 20, 2026 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant