Last updated 2026-08-26

Troubleshooting & Diagnostics

Identify and resolve common manifest resolution, local emulator, and deployment errors.

Troubleshooting & Diagnostics

This guide covers common diagnostic workflows and error resolution for Fluffy Core and Premium.

#Common Resolution Errors

#`E_CAPABILITY_UNBOUND`

Cause: Application source code attempts to access a database or topic that is not declared in fluffy-chainsaw.workspace.yaml.

Solution: Declare the missing resource in your application's runtime capabilities section and re-run:

sh
1fluffy-chainsaw generate --all

#Docker Daemon Connectivity

When running fluffy-chainsaw local, Fluffy requires a running Docker or Colima daemon.

If you encounter:

text
1error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock

Verify your Docker daemon status:

sh
1docker info

#Deployment Identity Mismatches

Each environment requires a distinct, cryptographically valid deployment.identity:

Caution
Never copy a deployment.identity from another team's workspace or environment. Always run fluffy-chainsaw init to generate a fresh identity for new environments.