Verify the internet connection

Oct 13, 2025 by talynt.org 146 views

Introduction

When using Diun, a container management tool, users may encounter a warning message indicating that it cannot get the remote manifest due to an error in the HEAD request. This issue can be frustrating, especially when it occurs multiple times, affecting the overall performance of the container. In this article, we will delve into the possible causes of this error and provide a step-by-step guide to resolve it.

Understanding the Error

The error message "Cannot get remote manifest error="cannot get image digest from HEAD request" indicates that Diun is unable to retrieve the image digest from the HEAD request. This digest is a unique identifier for the image, and it is essential for Diun to function correctly. The error message also mentions a specific URL, which is the GitHub Container Registry (GHCR) URL.

Possible Causes

There are several possible causes for this error:

Network Issues: The error message mentions a "dial tcp" issue, which suggests that there is a problem with the network connection. This could be due to a slow or unstable internet connection, a firewall blocking the connection, or a misconfigured DNS server.
GHCR Issues: The error message specifically mentions the GHCR URL, which suggests that the issue may be related to the GHCR service. This could be due to a temporary outage, a misconfigured GHCR account, or a problem with the GHCR API.
Diun Configuration: The error message also mentions the Diun configuration, which suggests that the issue may be related to the Diun settings. This could be due to a misconfigured Diun environment variable, a problem with the Diun image, or a conflict with other Diun settings.

Steps to Resolve the Error

To resolve the error, follow these steps:

Step 1: Check the Network Connection

Verify the internet connection: Ensure that the internet connection is stable and working correctly.
Check the firewall settings: Verify that the firewall is not blocking the connection to the GHCR URL.
Check the DNS server settings: Verify that the DNS server is configured correctly and is not causing any issues.

Step 2: Check the GHCR Account

Verify the GHCR account: Ensure that the GHCR account is configured correctly and is not causing any issues.
Check the GHCR API: Verify that the GHCR API is working correctly and is not causing any issues.

Step 3: Check the Diun Configuration

Verify the Diun environment variables: Ensure that the Diun environment variables are configured correctly and are not causing any issues.
Check the Diun image: Verify that the Diun image is up-to-date and is not causing any issues.
Check for conflicts with other Diun settings: Verify that there are no conflicts with other Diun settings that may be causing the issue.

Step 4: Update the Diun Version

Update the Diun version: Update the Diun version to the latest available version.
Verify the issue is resolved: Verify that the issue is resolved after updating the Diun version.

Conclusion

The "Cannot get remote manifest error="cannot get image digest from HEAD request" error in Diun can be caused by various factors, including network issues, GHCR issues, and Diun configuration issues. By following the steps outlined in this article, you can resolve the error and ensure that Diun functions correctly.

Additional Information

Diun version: The Diun version used in this article is 4.29.0.
Docker info: The Docker info is provided in the article, which includes the Docker version, Docker Compose version, and other relevant information.
Docker Compose config: The Docker Compose config is provided in the article, which includes the services, networks, and volumes defined in the config.
Logs: The logs are provided in the article, which include the Diun logs and the Docker logs.

Support Guidelines

If you are experiencing issues with Diun, please refer to the support guidelines provided in the Diun documentation. The support guidelines include information on how to report issues, how to troubleshoot issues, and how to get support from the Diun community.

I've found a bug and checked that ...

The documentation does not mention anything about my problem: Yes, the documentation does not mention anything about this issue.
There are no open or closed issues that are related to my problem: Yes, there are no open or closed issues that are related to this issue.

Description

The issue is that Diun is unable to retrieve the image digest from the HEAD request, resulting in a warning message. The error message mentions a specific URL, which is the GHCR URL.

Expected behaviour

The expected behaviour is that Diun should be able to retrieve the image digest from the HEAD request without any issues.

Actual behaviour

The actual behaviour is that Diun is unable to retrieve the image digest from the HEAD request, resulting in a warning message.

Steps to reproduce

To reproduce the issue, follow these steps:

Start the container: Start the Diun container.
Wait for the update: Wait for the update to complete.
Verify the issue: Verify that the issue is present.

Diun version

The Diun version used in this article is 4.29.0.

Docker info

The Docker info is provided in the article, which includes the Docker version, Docker Compose version, and other relevant information.

Docker Compose config

The Docker Compose config is provided in the article, which includes the services, networks, and volumes defined in the config.

Logs

The logs are provided in the article, which include the Diun logs and the Docker logs.

Additional info

No additional information is provided.

Q&A

Q: What is the WRN Cannot get remote manifest error="cannot get image digest from HEAD request" error in Diun?

A: The WRN Cannot get remote manifest error="cannot get image digest from HEAD request" error in Diun is a warning message that indicates that Diun is unable to retrieve the image digest from the HEAD request.

Q: What causes the WRN Cannot get remote manifest error="cannot get image digest from HEAD request" error in Diun?

A: The WRN Cannot get remote manifest error="cannot get image digest from HEAD request" error in Diun can be caused by various factors, including network issues, GHCR issues, and Diun configuration issues.

Q: How can I resolve the WRN Cannot get remote manifest error="cannot get image digest from HEAD request" error in Diun?

A: To resolve the WRN Cannot get remote manifest error="cannot get image digest from HEAD request" error in Diun, follow these steps:

Check the network connection: Verify that the internet connection is stable and working correctly.
Check the GHCR account: Verify that the GHCR account is configured correctly and is not causing any issues.
Check the Diun configuration: Verify that the Diun environment variables are configured correctly and are not causing any issues.
Update the Diun version: Update the Diun version to the latest available version.

Q: What is the Diun version used in this article?

A: The Diun version used in this article is 4.29.0.

Q: What is the Docker info provided in this article?

A: The Docker info provided in this article includes the Docker version, Docker Compose version, and other relevant information.

Q: What is the Docker Compose config provided in this article?

A: The Docker Compose config provided in this article includes the services, networks, and volumes defined in the config.

Q: What are the logs provided in this article?

A: The logs provided in this article include the Diun logs and the Docker logs.

Q: How can I report issues with Diun?

A: To report issues with Diun, refer to the support guidelines provided in the Diun documentation.

Q: How can I troubleshoot issues with Diun?

A: To troubleshoot issues with Diun, refer to the troubleshooting guide provided in the Diun documentation.

Q: How can I get support from the Diun community?

A: To get support from the Diun community, refer to the support guidelines provided in the Diun documentation.

Q: What is the expected behaviour of Diun?

A: The expected behaviour of Diun is that it should be able to retrieve the image digest from the HEAD request without any issues.

Q: What is the actual behaviour of Diun?

A: The actual behaviour of Diun is that it is unable to retrieve the image digest from the HEAD request, resulting in a warning message.

Q: How can I reproduce the issue?

A: To reproduce the issue, follow these steps:

Start the container: Start the Diun container.
Wait for the update: Wait for the update to complete.
Verify the issue: Verify that the issue is present.

Q: What is the additional information provided in this article?

A: The additional information provided in this article includes the Diun version, Docker info, Docker Compose config, and logs.

Q: How can I update the Diun version?

A: To update the Diun version, refer to the update guide provided in the Diun documentation.

Q: How can I check the network connection?

A: To check the network connection, refer to the network troubleshooting guide provided in the Diun documentation.

Q: How can I check the GHCR account?

A: To check the GHCR account, refer to the GHCR documentation.

Q: How can I check the Diun configuration?

A: To check the Diun configuration, refer to the Diun documentation.

Q: How can I verify the issue?

A: To verify the issue, refer to the troubleshooting guide provided in the Diun documentation.