📖 ~1 min read
Table of contents
Symptom & Impact
`podman build` aborts with `manifest unknown` for `registry.suse.com/bci/…`.
Environment & Reproduction
Reproduces on SLES 16 hosts that registered with SUSE but never authenticated to the registry.
Root Cause Analysis
BCI images require `podman login` with SCC credentials for entitled tags.
Quick Triage
Run `podman info` and confirm the configured search registries.
Step-by-Step Diagnosis
Try `podman pull registry.suse.com/bci/bci-base:latest` directly for clearer error output.

Solution – Primary Fix
Authenticate with `podman login registry.suse.com` using the SCC mirror credentials.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Mirror the BCI image into an internal Harbor/registry and pull from there.
Verification & Acceptance Criteria
Builds resolve `FROM` lines and produce a runnable image.
Rollback Plan
Remove cached layers (`podman image prune`) if the auth cache becomes inconsistent.
Prevention & Hardening
Manage registry credentials via configuration management, not ad-hoc logins.
Related Errors & Cross-Refs
Often paired with Kubernetes `ImagePullBackOff` from the same registry.
Related tutorial: View the step-by-step tutorial for sles-16.
View all sles-16 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
SUSE BCI container documentation.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.