[Starlingx-discuss] build-pkgs: package built failed , mock package missing

[Hu, Yong]

Abraham,
One more comment to this guide: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
We might have to add a session to update initial images, *if kernel or device modules are modified*.
Here are steps:
1). Run command: $ update-pxe-network-installer
After this is done, there should be 3 new files (vmlinuz, initrd.img and squashfs.img) generated in: $BUILD_FOLDER/pxe-network-installer/output
2). copy these 3 files into mirror “/import/mirrors/CentOS/tis-installer/” and put appropriate postfix. Note, the new info (images with the postfix) need to updated accordingly in in “build_srpm.data” and “pxe-network-installer.spec” under “cgcs-root/addons/wr-cgcs/layers/cgcs/mwa-beas/installer/pxe-network-installer/centos/”
3).  re-build pkgs and iso: (no need to make a clean build)


On 05/07/2018, 11:14 AM, "Liu, ZhipengS" <zhipengs.liu at intel.com> wrote:

    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 at intel.com] 
    Sent: 2018年7月4日 15:15
    To: Arce Moreno, Abraham <abraham.arce.moreno at intel.com>; Scott Little <scott.little at windriver.com>; starlingx-discuss at 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 at 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 at lists.starlingx.io
    http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss