Intel® Edge Software Hub
Get help on building Edge Software Hub solutions for edge compute node
Announcements
Welcome to the Intel Community! If you like the answer to your question, please mark it as 'Accepted Solution' to help others.

See our new article on Fidelity-first Ray Tracing in the Heterogeneous Compute Era.

The Edge Software Vision Package for Red Hat Enterprise Linux is now available here.

Learn more about developing on Intel® Hardware and Software here.

Castle Lake Manager Installation

Rajnish
Beginner
648 Views

Hi All

I am getting proxy related error while installing castle lake manager.I am attaching error screenshot along with /etc/environment .Looking for quick help.

PFA

 

 

 

Labels (1)
0 Kudos
9 Replies
Rajnish
Beginner
644 Views

I am adding docker proxy files as well.kindly have a look.

Any help would be appreciated.

Murni_J_Intel
Moderator
604 Views

Hi @Rajnish 

From the screen capture you attached seems like there is no error being throwing out, is that screen just hanging?

 

For the proxy configuration, you can refer to the below example

/etc/environment

HTTP_PROXY="<your_no_proxy_ip>:<port>"HTTPS_PROXY="<your_no_proxy_ip>:<port>"NO_PROXY="localhost,127.0.0.1,<System_1_IP,System_2_IP,System_3_IP,Virtual_IP"http_proxy="<your_no_proxy_ip>:<port>"https_proxy="<your_no_proxy_ip>:<port>"no_proxy="localhost,127.0.0.1,<System_1_IP,System_2_IP,System_3_IP,Virtual_IP"

I think you missin HTTP and HTTPS proxy setting. 

/etc/systemd/system/docker.service.d/http-proxy.conf

[Service]Environment="HTTP_PROXY=<your_no_proxy_ip>:<port>"Environment="NO_PROXY=localhost,127.0.0.1,<System_1_IP,System_2_IP,System_3_IP,Virtual_IP>"

 

/etc/systemd/system/docker.service.d/https-proxy.conf

[Service]Environment="HTTPS_PROXY=http://<your_proxy>:<port>/"Environment="NO_PROXY=localhost,127.0.0.1,<System_1_IP,System_2_IP,System_3_IP,Virtual_IP>"

 

~/.docker/config.json

{     "proxies":      {      "default":       {       "httpProxy": "<your_no_proxy_ip>:<port>"             "httpsProxy": "<your_no_proxy_ip>:<port>"       "noProxy": "localhost,127.0.0.1,<System_1_IP,System_2_IP,System_3_IP,Virtual_IP>"       }      }    }

 

please ensure that you follow the format for each file accordingly and it will be good if you can add all the system IP and virtual IP in the no_proxy setting to avoid any error for subsequence component installation as mentioned in the user guide. 

 

after done setting the proxy, you can run the below command to restart the docker service and reboot your system to ensure all the changes taking place before re-run the installation process. 

    $ sudo systemctl daemon-reload

    $ sudo systemctl restart docker

  

Rajnish
Beginner
599 Views

I am still getting following errors.could you please have a look into this.

Murni_J_Intel
Moderator
582 Views

HI @Rajnish 

Seems like the docker is having a connection issue.  Can you help to capture the proxy configuration for your docker service?

 

you can also try to verify the connectivity for the docker by using the below command 

$ sudo docker run -i -t --name test --rm ubuntu:bionic

$ apt-get update 

 

 

Rajnish
Beginner
574 Views

Hi Murmi

 

This is the output after running above command:-

root@slpr102:/home/meerssd# docker run -i -t --name test --rm ubuntu:bionic
Unable to find image 'ubuntu:bionic' locally
bionic: Pulling from library/ubuntu
Digest: sha256:fd25e706f3dea2a5ff705dbc3353cf37f08307798f3e360a13e9385840f73fb3
Status: Downloaded newer image for ubuntu:bionic
root@b9a3418c5a1d:/#

 

PFA

I am sharing docker proxy configuration files.

Murni_J_Intel
Moderator
565 Views

Hi, 

May I know if you already included the actual current machine IP in the no_proxy configuration as suggested? for the command from my previous post, can you help to run $ apt-get update after running $ sudo docker run -i -t --name test --rm ubuntu:bionic comamnd and share the output ? just now seems you only run one command. 

 

 

Rajnish
Beginner
555 Views

Hi Murmi

Yes i have already added the system proxy in the no_proxy configuration.

Below are the output of above mentioned commands:-

 

root@slpr102:/home/meerssd/edge_insights_industrial/Edge_Insights_for_Industrial_2.3.3/orchestrator/orchestrator/csl-prereq# docker run -i -t --name test --rm ubuntu:bionic
root@5a781bd56ec5:/# apt-get update
Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:3 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [15.8 kB]
Get:4 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [1370 kB]
Get:5 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [1815 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB]
Get:9 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [236 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1344 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [2243 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [2134 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [54.3 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [265 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages [11.3 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [11.4 kB]
Fetched 21.5 MB in 11s (1886 kB/s)
Reading package lists... Done

Rajnish
Beginner
534 Views

Hi Murmi,

i think apt-get was successful,based on the output can you please guide me the further.we need your support to make the csl manager up.

please let me know for further quarries.

Murni_J_Intel
Moderator
524 Views

Hi @Rajnish 

Based on the screenshot that you posted before, seems like you are using the root user for the installation.  You only need to use a normal user for this installation, for certain steps that require root permission we already add the "sudo" command in the user guide.

 

You can exit the root user and re-run the installation by using normal user, let me know if this is working on your side. 

Reply