Skip to main content

Build Failures

Common issues when greyhound builds container images from your source code.

Build Not Starting​

  • Config not found — Verify .greyhound/config.yaml exists on your PR branch, not just on main.
  • Build name mismatch — The image_from_build value in your service must exactly match a name in your builds array.
  • Repository access — greyhound needs access to the repository specified in repository. Check with the platform tools team.

Build Failing​

  • Dockerfile not found — If your Dockerfile isn't at the repo root, set the dockerfile field in your build config.
  • Build context — Make sure your build context includes all files needed by the Dockerfile.
  • Dependency issues — If builds fail during dependency installation, check that your package lock files are committed.

Build Succeeded but Service Won't Start​

  • Wrong port — The containerPort in your service config must match the port your application actually listens on.
  • Missing environment variables — Your app may require env vars that aren't set in the config.
  • Entrypoint issues — If using a custom command, make sure it's correct for your image.