starlingx/tools
Code Issues Proposed changes

Override builder images registry path

Browse Source 
Stx-tool always uses "stx-init-env --rebuild" from the docker hub
master branch. This causes random problems with people trying to
set up an environment

I used "stx-init-env --rebuild" to make sure the images are built
locally, it does not make sense to always use the latest tag for a
release.

TESTS
========================================

* Start stx-tools containers
* Pull an image inside "stx shell"
* Stop stx-tools container
* Run "stx-init-env" without the "--rebuild"
* to make sure the images are
  built locally

Story: 2010055
Task: 47970

Signed-off-by: Willy Njomen <willy.njomen@windriver.com>
Change-Id: Id466fbd243df1d77330473850fa4ba7d649941b7
This commit is contained in:
Willy Njomen 2023-05-08 14:36:35 -04:00
parent 5ffcf06ebe
commit 6d2105ae47
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
import-stx
View File

@ -69,6 +69,11 @@
# without the "--rebuild" flag.
# Default: master-debian-latest
# STX_PREBUILT_BUILDER_IMAGE_PREFIX
# Download pre-built images from this registry/prefix. This is used by "stx-init-env"
# without the "--rebuild" flag. If not empty, this must end with "/".
# Default:starlingx/
notice_warn () {
local tty_on tty_off
if [[ -t 2 ]] ; then

2
stx-init-env
View File

@ -54,7 +54,7 @@ HELM=helm
DOCKER=docker
PYTHON3=python3
KUBECTL=kubectl
DOCKER_PREFIX="starlingx/"
DOCKER_PREFIX=${STX_PREBUILT_BUILDER_IMAGE_PREFIX:-'starlingx/'}
DOCKER_IMAGES="stx-builder stx-pkgbuilder stx-lat-tool stx-aptly"
DOCKER_TAG="$STX_PREBUILT_BUILDER_IMAGE_TAG"