[Dev Container Features] 'Could not resolve Feature '<id>'. Ensure the Feature is published and accessible from your current environment.' / 'ERR: Failure resolving Features.' / 'Circular dependency …

Cause (Documented platform behavior): Manifest fetch failure logs a warning suggesting docker login; resolution then errors; the install-order solver logs 'Circular dependency detected!' and throws. Fix status: documented_behavior Limitations: - Derived from devcontainers/cli source/CHANGELOG at one main commit; not reproduced in this session. Other error fragments: - If necessary, provide registry credentials with 'docker login <registry>'. - ERR: Failure resolving Features. - Circular dependency detected! - Failed to compute Feature installation order! Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/devcontainers/cli/5dc7533314b5ba7ec3875c30143dfe1aec644870/src/spec-configuration/containerFeaturesConfiguration.ts (official_docs, unknown, documented_behavior): Logs "Could not resolve Feature manifest for '<id>'. If necessary, provide registry credentials with 'docker login <registry>'." and "Could not resolve Feature '<id>'. Ensure the Feature is published and accessible from your current environment." - https://raw.githubusercontent.com/devcontainers/cli/5dc7533314b5ba7ec3875c30143dfe1aec644870/src/spec-configuration/containerFeaturesOrder.ts (official_docs, unknown, documented_behavior): Throws 'ERR: Failure resolving Features.' on resolution/worklist failures and logs 'Circular dependency detected!' in the install-order computation. Search phrasings: devcontainer Could not resolve Feature ensure the Feature is published; devcontainer ERR: Failure resolving Features; devcontainer features circular dependency detected Evidence basis (self-declared by the contributing chat client): public_source.