[meta-xilinx] Working behind proxy issue

[Gielmuda, Pawel (GE Aviation)]

Hi,
We are currently working on TSN Endpoint Ethernet MAC based on Yocto software. We would like to use it in Petalinux .
I have a problem with compilation of Yocto software given in TSN package. It’s probably associated with my network/linux configuration.

The compilation needs access to internet to sync and configure Yocto packets.  What’s more  it requires special setup of network proxy.
I fallow:
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
because we have corporate network with proxy server. Unfortunately both shown ways fails. I google internet and ask IT helpdesk for help but no one was able to help me.


Some more technical details of my problem.

I have such working configuration:
-------------------------------------------------------
|      Corporate Network (with proxy)       |
|    -----------------------------------------------   |
|   |          My PC with windows 10        |   |
|   |   ----------------------------------------    |   |      ----- >  Internet
|   |   |Ubuntu 16.04 on VirtualBox |   |   |
|   |   ----------------------------------------    |   |
|   -----------------------------------------------     |
-------------------------------------------------------

Like I said the problem is with Linux configuration. According to  this page<https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy> there are two methods of resolving this.
In the first method shown in this page<https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy> the problem starts when I try to copy repository with command:

[$ git clone git://gitenterprise.xilinx.com/syeds/Yocto_TSN.git   Cloning into 'Yocto_TSN'...  2018/06/27 09:09:36 socat[4021] E socks: undefined status 84  fatal: Could not read from remote repository.    Please make sure you have the correct access rights  and the repository exists.]
I can skip this step and download that manually but this problem repeats when I do other steps of tutorial.
The internet says it’s a problem with my linux configuration (proxy and system variables). Because of that I attach my snippet ~./bashrc which set all of those variables/proxies. I’m sure they are applied – I double checked that.


The second method shown in this page<https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy> is based on docker tool. After installation of docker when I try basic “Hello world” application in docker I get:
[$ sudo docker run hello-world  Unable to find image 'hello-world:latest' locally  latest: Pulling from library/hello-world  9bb5a5d4561a: Pulling fs layer   docker: error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/e3/e38bc07ac18ee64e6d59cf2eafcdddf9cec2364dfe129fe0af75f1b0194e0c96/data?verify=1530086455-UFtW5CTudPvDsXjStSN3%2Frc5DhA%3D: x509: certificate signed by unknown authority.  See 'docker run --help'.]

I think this has influence on the step 4 in https://github.com/crops/chameleonsocks which is required for this method. That step ends with an error:
[2018-06-27 09:12:58 (2,39 MB/s) - ‘chameleonsocks-1.2.tar.gz’ saved [116649086/116649086]    Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.27/images/load?quiet=0: dial unix /var/run/docker.sock: connect: permission denied  Downloading crops/chameleonsocks:1.2 failed]

So I stuck in both of this methods and already look through the internet. Any tip will be most helpful.

Snippet of ~./bashrc:
export http_proxy='http://http-proxy.my.corporate.com:80/'
export https_proxy='https://http-proxy.my.corporate.com:80/'
export ftp_proxy='http://http-proxy.my.corporate.com:80/'
export ALL_PROXY='socks://http-proxy.my.corporate.com:80/'
export all_proxy='socks://http-proxy.my.corporate.com:80/'
export no_proxy='my.corporate.com'
export PATH=~/bin:$PATH
export GIT_PROXY_COMMAND="oe-git-proxy"
export NO_PROXY=$no_proxy

Regards
Pawel Gielmuda

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20180627/06631485/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 27012 bytes
Desc: image001.png
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20180627/06631485/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 51170 bytes
Desc: image002.png
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20180627/06631485/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 33128 bytes
Desc: image003.png
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20180627/06631485/attachment-0005.png>