Quick Fixes for Docker's Manifest Not Found Error

👋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:

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.

💡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