The artifacts generated by the Liberty App Accelerator and Bluemix developer CLI build upon the developer licensed Docker image from Docker Hub. Prior to deployment to a production environment, users must switch to use a Docker image that contains a production licensed version of Liberty. There are two routes for entitled customers to obtain a production licensed Docker image:

  1. Upgrading the developer licensed image from Docker Hub using a license upgrade JAR obtained from Passport Advantage.
  2. Building your own production licensed image from scratch using binaries from Passport Advantage.

The first approach is the simplest but the second provides more flexibility if, for example, you have specific requirements about the version of Liberty or base operating system to use. Details of the steps required for each of these approaches can be found in the following README: https://github.com/WASdev/ci.docker/blob/master/ga/README.md

Once you have built the production licensed image, push it to a Docker registry where it will be accessible to both development and production build environments. This might be the registry provided with IBM Cloud private, the IBM Bluemix Container Registry, or another third-party registry. Next, update the Dockerfile generated by the Liberty App Accelerator or Bluemix developer CLI to modify the FROM command to specify your production licensed image.

If the registry that you have chosen requires authentication, developers will need to perform a Docker login before performing a local build. When installing the Microservice Builder pipeline you can specify a variable Pipeline.Registry.Secret that gives the name of a Kubernetes registry secret. This secret needs to contain the authorization token for the registry specified in Pipeline.Registry.Url to which the built image is pushed and, if different, the registry containing your base image.

Join The Discussion

Your email address will not be published. Required fields are marked *