Hi Gerry & Penny:

     Thanks a lot you. This is very useful for me .

 

BR
Austin Sun.

 

From: Kopec, Gerald (Gerry) [mailto:Gerry.Kopec@windriver.com]
Sent: Wednesday, May 1, 2019 6:35 AM
To: Penney, Don <Don.Penney@windriver.com>; Little, Scott <Scott.Little@windriver.com>; starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Build Docker images and how to use temporary image for debug in deploy env.

 

To load a private docker image onto your controller try these instructions:

https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages#Testing_Image_on_Running_System

 

Then follow recommended link to:

https://wiki.openstack.org/wiki/StarlingX/Containers/FAQ#How_do_I_make_changes_to_the_code_or_configuration_in_a_pod_for_debugging_purposes.3F

 

Gerry

 

From: Penney, Don
Sent: Tuesday, April 30, 2019 5:41 PM
To: Little, Scott; starlingx-discuss@lists.starlingx.io
Cc: Kopec, Gerald (Gerry)
Subject: RE: [Starlingx-discuss] Build Docker images and how to use temporary image for debug in deploy env.

 

Sorry, Austin, I didn’t see your email this morning.

 

#1:

The stx-mariadb image is not built in the dev build stream, much like other images. It now only builds in stable. The stx-fm-rest-api image, as well, only builds in the stable stream.

 

The error you’re getting is because there are a couple of centos_dev_docker_images.inc files with stale entries. This is just a warning to stderr and should not impact anything.

 

#2:

You can use the --push option of build-stx-images.sh, combined with --user and --registry options to tag and push the image(s) to a private registry or the docker hub. From there, I think there are instructions available on loading those images onto your controller.

 

Gerry, are those instructions on a wiki?

 

 

From: Scott Little [mailto:scott.little@windriver.com]
Sent: Tuesday, April 30, 2019 5:02 PM
To: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Build Docker images and how to use temporary image for debug in deploy env.

 

CENGN isn't building dev images these days.  So it's not being tested in a while.

 

 

cat stx/stx-integ/centos_dev_docker_images.inc
   database/mariadb

 

However there is no file ...

   stx/stx-integ/database/mariadb/centos/stx-mariadb.dev_docker_image

 

that's definitely inconsistent.  Raise a launchpad.

 

Scott

 

 

On 2019-04-30 5:17 a.m., Sun, Austin wrote:

Hi All:

1) When I tried to build dev images . I meet below error.  

    “Unsupported BUILDER in /home/wrsroot/starlingx/workspace/localdisk/designer/wrsroot/starlingx/cgcs-root/stx/stx-integ/database/mariadb/centos/*.dev_docker_image:”

Build command is something like (sudo ./build-stx-images.sh --os centos --stream dev --base starlingx/stx-centos:master-dev-latest --wheels ~/starlingx/wheel/stx-centos-stable-wheels.tar --only stx-fm-rest-api)

 

Does mariadb not support for dev build ?

 

2) how to push image built by developer to deployed environment  directly ?

    

    Do we have any wiki or guide about this ?  

 

Thanks.

BR
Austin Sun.

 

 

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss