[Starlingx-discuss] Starlingx iso [BUILD]

[Scott Little]

These fixes have merged to address download_mirror.sh failures on our 
supported branches...

     master: https://review.opendev.org/c/starlingx/tools/+/866071
     r/stx.6.0: https://review.opendev.org/c/starlingx/tools/+/866072
    r/stx.7.0: https://review.opendev.org/c/starlingx/tools/+/866073

The download_mirror.sh script should be run inside the build container.

The official documentation has moved here....

https://docs.starlingx.io/developer_resources/build_guide.html

and you can navigate back to old release documentation with the '<<' and 
'>>' buttons at the upper right.
e.g. for for stx.6.0 you can navigate to...

https://docs.starlingx.io/releasenotes/r6-0-release-notes-bc72d0b961e7.html

The source code for the documentation can be found here ...

cgcs-root/stx/docs/doc/source/developer_resources/

Your appear to be quoting from 'tools/README.rst' which is unmaintained, 
and ought to have been deleted or reduced to pointers to the official docs.
Please file a LaunchPad to fix or remove the misleading document.

Hope this helps!

Scott



On 2022-11-27 19:10, Outback Dingo wrote:
> 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 here is where we find the problems
>
> tb.sh create .... ok
> tb,sh exec ..... ok
>
> so reading this i think slim clarification is needed, do we run
>
> centos-mirror-tools/download_mirror.sh outside the container?
>
> Package mirror creation
> Once the StarlingX docker image has been built, you must create a
> mirror before creating the ISO image. Basically, a mirror is a
> directory that contains a series of packages. The packages are
> organized to be consumed by the ISO creation scripts.
>
> The HOST_MIRROR_DIR variable provides the path to the mirror. The
> buildrc file sets the value of this variable unless the localrc file
> has modified it.
>
> The mirror creation involves a set of scripts and configuration files
> required to download a group of RPMs, SRPMs, source code packages and
> so forth. These tools live inside centos-mirror-tools directory.
>
> All items included in this directory must be visble inside the
> container environment. Then the container shall be run from the same
> directory where these tools are stored. Basically, we run a container
> with the previously created StarlingX docker image, using the
> following configuration:
>
> As /localdisk is defined as the workdir of the container, the same
> folder name should be used to define the volume. The container will
> start to run and populate logs and output folders in this directory.
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io