ollama - 💡(How to fix) Fix Can't pull or run through Starlink [3 comments, 3 participants]

Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/99/9999d473417a8e179d993498195be5f42cab963acc75f4a6b15d981e8b68abed/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%2F20260329%2Fauto%2Fs3%2Faws4_request&X-Amz-Date=20260329T085126Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=d6a03e3fe12f561ccfe3a95d94554d94223d7168c6af43bbe083c04e2687413a": dial tcp x.y.z.e:443: i/o timeout

Fix Plan

The issue seems to be related to network connectivity and timeouts. To resolve this, we'll focus on adjusting the Docker configuration to increase the timeout values and improve network stability.

Step-by-Step Solution:

1. Increase Docker timeout values:

   • Edit the Docker configuration file (~/.docker/daemon.json) and add the following lines:

     {
       "debug": true,
       "experimental": false,
       "execRoot": "",
       "httpProxy": "",
       "httpsProxy": "",
       "dns": [],
       "dnsSearch": [],
       "tls": true,
       "tlsVerify": true,
       "tlsCert": "",
       "tlsKey": "",
       "mtu": 0,
       "bridge": "",
       "containerd": {
         "env": [
           "http_proxy=http://proxy:8080",
           "https_proxy=http://proxy:8080"
         ]
       },
       "registry-mirrors": [],
       "insecure-registries": [],
       "debug": true,
       "experimental": false,
       "execRoot": "",
       "data-root": "",
       "max-concurrent-downloads": 3,
       "max-concurrent-uploads": 5,
       "max-download-attempts": 5
     }

   • Specifically, adjust the max-download-attempts value to a higher number (e.g., 10) to increase the number of retries.

2. Adjust network settings for Docker:

   • Ensure your Docker installation is configured to use the correct network settings. You can do this by setting the http_proxy and https_proxy environment variables.

3. Restart Docker:

   • After making these changes, restart the Docker service to apply the new configuration:

     sudo systemctl restart docker

Verification

To verify that the fix worked, attempt to pull and run a model using Starlink. If the issue persists, check the Docker logs for any errors related to network connectivity or timeouts.

Extra Tips

• Ensure your network connection is stable and that there are no firewall rules blocking the Docker traffic.
• Consider using a VPN or a proxy server to improve network stability if you're experiencing issues with your internet connection.
• Regularly update your Docker installation and dependencies to ensure you have the latest security patches and features.