Quick Fixes for Docker's Manifest Not Found Error

Amit KumarAmit Kumar
5 min read

👋Introduction

I was working on setting up Sitecore Headless using Docker, and was using the following Sitecore version with Sitecore modules and the host machine:

Sitecore VersionSitecore 10.3
Sitecore ModulesSitecore PowerShell Extension, Sitecore Experience Accelerator (SXA), Sitecore Headless Services
Host MachineWindows 11 Enterprise (23H2)
Container Image Versionltsc2019 - Long-Term Servicing Channel (LTSC) release of Windows Server 2019

This Sitecore instance was running fine earlier and recently started getting the error "Error response from daemon: manifest not found." This article will explain why this error happens and offer simple solutions to help you get your Docker containers working properly.

💡
You can find more information about Sitecore Docker Setup here.

💡Understanding the Manifest Not Found Error

The "manifest not found" error occurs when Docker is unable to find the manifest file for a specific image. The manifest file contains essential information about the image, such as its architecture, operating system, and layers. 🔝

Error Details:

[+] Running 2/4

- solr [⣿⣿⣿] Pulling            2.6s

- mssql [⠀] Pulling              2.6s

- traefik Pulling                                                                    2.6s

manifest for traefik:v2.2.0-windowsservercore-1809 not found: manifest unknown: manifest unknown

Waiting for CM to become available...

Invoke-RestMethod : Unable to connect to the remote server

At C:\Contoso\up.ps1:88 char:19

+ ...   $status = Invoke-RestMethod "http://localhost:8079/api/http/routers ...

+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo: InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest

   ) [Invoke-RestMethod], WebException

    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands

   .InvokeRestMethodCommand

😞Causes of the Manifest Not Found Error

  1. Incorrect Image Name or Tag: Typos or incorrect image names can lead to this error.

  2. Image Not Found in Registry: The image may not exist in the Docker registry.

  3. Docker Version Incompatibility: Using an outdated Docker version can cause compatibility issues.

  4. Corrupted Image or Cache: Corrupted images or cache can prevent Docker from finding the manifest. 🔝

⚡Solutions to Fix the Manifest Not Found Error

Solution 1: Verify Image Name and Tag

  1. Check the image name and tag for typos.

  2. Use the docker images command to list available images.

  3. Verify the image name and tag using docker inspect .

Solution 2: Check Docker Registry

  1. Search for the image on Docker Hub or other registries.

  2. Ensure the image exists and is publicly available.

Solution 3: Update Docker Version

  1. Check the current Docker version using docker --version.

  2. Update Docker to the latest version. 🔝

Solution 4: Clear Docker Cache

  1. Run docker system prune to clear unused data.

  2. Remove dangling images using docker images -f dangling=true.

🕵️Troubleshooting Steps

  1. Check Docker Logs: Run docker logs to identify potential issues.

  2. Verify Docker Configuration: Check Docker configuration files for errors.

  3. Restart Docker Service: Restart the Docker service.

After a thorough check, I found out that the issue was due to a wrong image name for Traefik. So, I changed the Traefik image from traefik:v2.2.0-windowsservercore-1809 to traefik:v3.2-windowsservercore-1809, and restarted the setup after removing all the images.

🔐Prevention Measures

To minimize the chances of encountering this error in the future:

  1. Regularly Update Docker: Stay up-to-date with the latest Docker version.

  2. Verify Image Integrity: Check image integrity before pulling.

  3. Use Docker Hub: Use official Docker Hub images.

  4. Use Docker Compose files to version your image references

🔦Conclusion

The "manifest not found" error can be resolved by following these step-by-step solutions. By understanding the causes and troubleshooting steps, you'll be able to fix this error and ensure smooth Docker operations. 🔝

To learn more about setting up Sitecore Docker Containers and how to upgrade them, you can find detailed information in the resources below:

🙏Credit/References

🏓Pingback

Sitecore Experience PlatformSitecore Experience Accelerator 10.4.0When was Sitecore 10 released?
What is Sitecore 10?When was Sitecore 9.3 released?What does Sitecore do?
sc-packages - Sitecore.Kernel 10.4.0Sitecore Product Support LifecycleWhat's New In Sitecore 10.4 & The Future of Sitecore
Sitecore Products and ModulesSitecore Installation and Upgrade GuidesSitecore image reference
Sitecore Developer PortalConfiguring Sitecore Next.js Headless SXA Multisite App in a Sitecore Container - Amit's Blog (amitkumarmca04.blogspot.com)sitecore jss nextjs
sitecore jamstackDefault topologies Sitecore DocumentationSolutions for your digital experiences
XM topology for on-premisesInstallation Guide for the XM Scaled TopologyContainer tips and improvements for Sitecore Developers
What is Sitecore Experience Manager?Sitecore configurations and topology for AzureUsing CMS-only mode to run Sitecore without the xDBThe xDB and tracker configuration settings
Sitecore Experience Platform - Content Management SystemSitecore topologies 🔝What is the default topology of Sitecore?
Sitecore StreamWhat is the difference between Sitecore XM and XP?Sitecore Stream Features
Sitecore Stream ArchitectureSitecore Managed Cloud Standard – topologies and tiersInstallation Guide for the XP Scaled topology
Sitecore Managed Cloud TopologiesPaaS topologies and tiers for Sitecore XP 10.0 and higherSitecore JSS Topologies
Installation Guide for the XM Scaled TopologyAdjust Sitecore topology based on resource usage 🔝Topologies for Sitecore Azure Deployments
sitecore latest versionsitecore latest version downloadsitecore xp latest version
sitecore powershell get latest version of itemsitecore get latest version of itemsitecore sxa latest version
sitecore jss latest versionsitecore xm latest versionsitecore cms latest version
sitecore containerssitecore-containers-prerequisitessitecore containers github
sitecore 10.3 containerssitecore 10 certification costsitecore support dates
sitecore container deploymesitecore container registrysitecore container support package
sitecore containers documentationsitecore docker container unhealthysitecore container deployment package
sitecore docker containerssitecore container imagescontainers in sitecore
sitecore jss dockersitecore kubernetes 🔝sitecore linux containers
sitecore on containerssitecore container registry (scr)sitecore container setup
sitecore sxa containersitecore 10 containersupgrade sitecore 9 to 10
0
Subscribe to my newsletter

Read articles from Amit Kumar directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Amit Kumar
Amit Kumar

My name is Amit Kumar. I work as a hands-on Solution Architect. My experience allows me to provide valuable insights and guidance to organizations looking to leverage cutting edge technologies for their digital solutions.As a Solution Architect, I have extensive experience in designing and implementing robust and scalable solutions using server-side and client-side technologies. My expertise lies in architecting complex systems, integrating various modules, and optimizing performance to deliver exceptional user experiences. Additionally, I stay up-to-date with the latest industry trends and best practices to ensure that my solutions are always cutting-edge and aligned with business objectives.