You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote:
Hi Abraham,
When I followed your guide, there are 3 issues I found.
1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis-Centos-7-Distro enabled=1 baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found.
2) In Download Source Code Repositories step of the guide. cgcs-dl $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads // change to $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/
3) lighttpd not started by default in build container, and also could not started manually.
=============================================================== Raised below 2 stories. 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto 2002938 lighttpd not started by default in build container
BRs zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2018年7月5日 11:14 To: Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham,
When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection
It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote:
> > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned.
Cool! Thank you!
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss