You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because ocl-icd-2.2.12-1.el8.x86_64.rpm is downloaded through an HTTP channel (here), the building process might fail on OpenShift if the cluster has http and https proxies configured.
BuildConfigs in OpenShift set HTTP_PROXY and HTTPS_PROXY environment values automatically, but not http_proxy.
Build process output suggests that rpm -ivh is using curl under the hood for the download. curl is notorious for using lowercase http_proxy when establishing an HTTP connection (in contrast to HTTPS where both uppercase and lowercase work).
The best way would be to download ocl-icd-2.2.12-1.el8.x86_64.rpm through an HTTPS channel (though it seems like mirror.centos.org doesn't allow HTTPS access).
As a workaround, it seems like adding http_proxy=${HTTP_PROXY} in front of the the command that does the installation of ocl-icd from http://mirror.centos.org would be enough to fix the problem, but there might be a better and cleaner solution.
The text was updated successfully, but these errors were encountered:
Because
ocl-icd-2.2.12-1.el8.x86_64.rpm
is downloaded through an HTTP channel (here), the building process might fail on OpenShift if the cluster has http and https proxies configured.BuildConfigs in OpenShift set HTTP_PROXY and HTTPS_PROXY environment values automatically, but not http_proxy.
Build process output suggests that
rpm -ivh
is usingcurl
under the hood for the download.curl
is notorious for using lowercasehttp_proxy
when establishing an HTTP connection (in contrast to HTTPS where both uppercase and lowercase work).The best way would be to download
ocl-icd-2.2.12-1.el8.x86_64.rpm
through an HTTPS channel (though it seems like mirror.centos.org doesn't allow HTTPS access).As a workaround, it seems like adding
http_proxy=${HTTP_PROXY}
in front of the the command that does the installation of ocl-icd fromhttp://mirror.centos.org
would be enough to fix the problem, but there might be a better and cleaner solution.The text was updated successfully, but these errors were encountered: