Dagger "input:" GraphQL error in CI

Dagger pipelines are GraphQL queries against the engine. An "Error: input:" prefix means the engine returned an error for the query, either a schema mismatch (bad field/argument) or a runtime failure inside a step the query drove.

What this error means

dagger fails with "Error: input: ..." followed by the field path, for example a container exec that exited non-zero or an unknown argument.

Error: input: container.from.withExec.stdout process "sh -c npm test" did not complete successfully: exit code: 1

Common causes

A step in the pipeline failed

The GraphQL path names the operation that failed, such as a withExec whose command exited non-zero. The step is the real error.

A schema mismatch in the query

An unknown field or argument, often from a CLI/SDK version that does not match the engine, is rejected by the engine schema.

How to fix it

Trace the failing field path

1. Read the GraphQL path in the "input:" error to find the failing operation.
2. If it is a withExec, run that command directly to see its output.
3. If it is an unknown field, align the SDK/CLI with the engine version.

dagger call test --output=./report stderr

Match SDK and engine versions

Schema errors on valid code usually mean a version skew. Align the SDK and CLI with the engine.

How to prevent it

• Pin SDK, CLI, and engine to compatible versions.
• Read the GraphQL path to locate the failing step fast.
• Reproduce failing withExec commands directly.

Related guides