singularity ecosystem pause

singularity ecosystem pause --state-dir STATE --json

The owner records the pause and a control record, then answers with [status](/docs/cli/ecosystem/status). New selection, dispatch, provisioning, release and outcome review stop; observation and reconciliation of already dispatched work continue. The pause survives restarts. It is not cancellation of a remote operation.

Shared control options

--state-dir PATH names the live owner's state directory; its environment equivalent is SINGULARITY_STATE_DIR. It is required: no directory is assumed. --json prints the whole response envelope; without it a successful answer prints only its result, and a refusal prints the whole envelope.

The owner and the client must run as the same Unix user. An owner that is not listening is a refusal — ecosystem owner unavailable at <socket>: <error>; no cached state is presented as live — and every refusal exits nonzero.