guyuqi commented on PR #961:
URL: https://github.com/apache/bigtop/pull/961#issuecomment-1193485005

   Failed to build bigtop/puppet: fedora-36 docker image:
   
   ```
   Errors during downloading metadata for repository 'fedora':
     - Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64 
[getaddrinfo() thread failed to start]
   Error: Failed to download metadata for repo 'fedora': Cannot prepare 
internal mirrorlist: Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64 
[getaddrinfo() thread failed to start]
   Fedora 36 - x86_64                              0.0  B/s |   0  B     00:00
   Errors during downloading metadata for repository 'fedora':
     - Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64 
[getaddrinfo() thread failed to start]
   Error: Failed to download metadata for repo 'fedora': Cannot prepare 
internal mirrorlist: Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64 
[getaddrinfo() thread failed to start]
   Fedora 36 - x86_64                              0.0  B/s |   0  B     00:00
   Errors during downloading metadata for repository 'fedora':
     - Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64 
[getaddrinfo() thread failed to start]
   Error: Failed to download metadata for repo 'fedora': Cannot prepare 
internal mirrorlist: Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64 
[getaddrinfo() thread failed to start]
   /tmp/puppetize.sh: line 31: puppet: command not found
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to