Any update on this ? Davlet ? Do you understand the issue that ScottK is having ? Is it reproducible in your environment ? Or do you need to take a look at ScottK's environment ? Greg. -----Original Message----- From: Outback Dingo <outbackdingo@gmail.com> Sent: Thursday, May 2, 2024 1:34 PM To: Panech, Davlet <Davlet.Panech@windriver.com> Cc: starlingx-discuss@lists.starlingx.io; Little, Scott <Scott.Little@windriver.com> Subject: Re: StarlingX build tools CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. ok great, at least i can start working through it again, though following the document... i get hung up at stx shell STX-k8s - INFO: Running: minikube -p minikube-dingo kubectl -- get pods --selector 'app.kubernetes.io/instance=stx-env,app.kubernetes.io/name=stx-builder' | awk '$3 == "Running" {print $1}' | tail -n 1 /root/localrc: line 21: syntax error near unexpected token `newline' /root/localrc: line 21: `export GITEMAIL=<scottk@optimcloud.com>' and it never gets a shell On Thu, May 2, 2024 at 8:56 PM Panech, Davlet <Davlet.Panech@windriver.com> wrote:

Hi,

The official build tools documentation is indeed out of date. We are working on updating it, in the meanwhile there's a Wiki page that describes the process of building the packages and the ISO: https://wiki.openstack.org/wiki/StarlingX/DebianBuildEnvironment

Hope this helps, D.

________________________________ From: Outback Dingo <outbackdingo@gmail.com> Sent: Wednesday, April 24, 2024 11:24 AM To: starlingx-discuss@lists.starlingx.io <starlingx-discuss@lists.starlingx.io>; Little, Scott <Scott.Little@windriver.com> Subject: StarlingX build tools

CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe.

this is the problem area, as it is all based on CentOS ...using https://opendev.org/starlingx/tools

cd localdisk && bash download_mirror.sh download_mirror.sh: line 8: /localdisk/../toCOPY/lst_utils.sh: No such file or directory download_mirror.sh: line 279: merge_lst: command not found download_mirror.sh: line 280: merge_lst: command not found download_mirror.sh: line 281: merge_lst: command not found download_mirror.sh: line 282: merge_lst: command not found download_mirror.sh: line 283: merge_lst: command not found -------------------------------------------------------------- WARNING: this script HAS TO access internet (http/https/ftp), so please make sure your network working properly!! step #0: Configuring yum repos ... /localdisk/make_stx_mirror_yum_conf.sh -R -d /tmp/stx_mirror_QF20M6 -y /localdisk/yum.conf.sample -r /localdisk/yum.repos.d -D -l \cp -r '/localdisk/yum.repos.d/*' '/tmp/stx_mirror_QF20M6/yum.repos.d/' \cp '/localdisk/yum.conf.sample' '/tmp/stx_mirror_QF20M6/yum.conf'

from the document

Download packages Inside the Docker container, enter the following commands to download the required packages to populate the CentOS mirror repository:

$ cd localdisk && bash download_mirror.sh

Monitor the download of packages until it is complete. When the download is complete, the following message appears:

totally 17 files are downloaded! step #3: done successfully IMPORTANT: The following 3 files are just bootstrap versions. Based on them, the workable images for StarlingX could be generated by running "update-pxe-network-installer" command after "build-iso" - out/stx/CentOS/Binary/LiveOS/squashfs.img - out/stx/CentOS/Binary/images/pxeboot/initrd.img - out/stx/CentOS/Binary/images/pxeboot/vmlinuz

Verify packages Verify no missing or failed packages exist:

$ cat logs/_missing_.log $ cat logs/_failmove_.log

In case missing or failed packages do exist, which is usually caused by network instability (or timeout), you need to download the packages manually. Doing so assures you get all RPMs listed in rpms_3rdparties.lst/rpms_centos.lst/rpms_centos3rdparties.lst.

Copy the files to the mirror After all downloads are complete, copy the downloaded files to mirror.

$ find ./output -name "*.i686.rpm" | xargs rm -f $ chown 751:751 -R ./output $ cp -rf output/stx/ <your_mirror_folder>/

In this case, <your_mirror_folder> can be whatever folder you want to use as mirror.

Tweaks in the StarlingX build system. NOTE: You do not need to do the following step if you've synced the latest codebase.

Go into the StarlingX build system (i.e. another container that hosts the build system) and perform the following steps: