You can use this command to fix the limitation issue in your build container (CentOS):

 

sudo sed -i 's/nr_inodes=0/nr_inodes=100k/g' /usr/lib/python2.7/site-packages/mockbuild/plugins/tmpfs.py

 

 

From: "Liu, Changcheng" <changcheng.liu@intel.com>
Date: Monday, 26 November 2018 at 9:28 AM
To: "Hu, Yong" <yong.hu@intel.com>, Erich Cordoba <erich.cm.lists@yandex.com>, "'starlingx-discuss@lists.starlingx.io'" <starlingx-discuss@lists.starlingx.io>, "Cordoba Malibran, Erich" <erich.cordoba.malibran@intel.com>
Subject: RE: [Starlingx-discuss] stx-tools: setup stx build environment

 

Hi Yong,

Yes. The proxy should be right. But the error is still there.

 

BTW, I also hit below error:

09:23:46 b3: INFO: mounting tmpfs at /localdisk/loadbuild/nstcc1/starlingx/std/mock/b3/root.

09:23:46 b3: ERROR: Command failed:

09:23:46 b3:  # mount -n -t tmpfs -o mode=0755 -o nr_inodes=0 -o size=11g mock_chroot_tmpfs /localdisk/loadbuild/nstcc1/starlingx/std/mock/b3/root

 

B.R.

Changcheng

From: Hu, Yong
Sent: Monday, November 26, 2018 9:10 AM
To: Liu, Changcheng <changcheng.liu@intel.com>; Erich Cordoba <erich.cm.lists@yandex.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>; Cordoba Malibran, Erich <erich.cordoba.malibran@intel.com>
Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment

 

Your no_proxy env setting should resolve the following error, are you still seeing it?

21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable

 

From: "Liu, Changcheng" <changcheng.liu@intel.com>
Date: Sunday, 25 November 2018 at 3:24 PM
To: Erich Cordoba <erich.cm.lists@yandex.com>, "'starlingx-discuss@lists.starlingx.io'" <starlingx-discuss@lists.starlingx.io>, "Cordoba Malibran, Erich" <erich.cordoba.malibran@intel.com>
Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment

 

Hi Erich,

Is there anything wrong with proxy env in container as below?

[nstcc1@d8ae703a2a91 /]$ env | grep -i proxy

NO_PROXY=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8

http_proxy=http://child-prc.intel.com:913

FTP_PROXY=ftp://child-prc.intel.com:913

ftp_proxy=ftp://child-prc.intel.com:913

https_proxy=http://child-prc.intel.com:913

HTTPS_PROXY=http://child-prc.intel.com:913

no_proxy=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8

HTTP_PROXY=http://child-prc.intel.com:913

 

B.R.

Changcheng

 

 

From: Erich Cordoba [mailto:erich.cm.lists@yandex.com]
Sent: Friday, November 23, 2018 9:37 PM
To: 'starlingx-discuss@lists.starlingx.io' <
starlingx-discuss@lists.starlingx.io>; Cordoba Malibran, Erich <erich.cordoba.malibran@intel.com>; Liu, Changcheng <changcheng.liu@intel.com>
Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment

 

Hi Liu, 

 

As you need to setup a proxy, you need also to set the no_proxy=127.0.0.1 env variable, so mock can find the internal repository.

 

This is something that we need to do in our internal build job.

 

-Erich

--
Sent from Yandex.Mail for mobile