Introduction

This procedure covers the action to generate the BOA image for deployment using the available BOA packages.

Note: References to s2boa included for completeness regarding the installation of a tailored BOA.

Pre-conditions

1. Procedure Install BOA in development mode from scratch has been successfully executed.

Procedure

1. Change user to root:

sudo su -

1. Export path to resources:

   Note: this path is where the repositories for eboa, vboa, the tailored BOA and ORC packages are located.

export PATH_TO_RESOURCES=PATH_TO_REPOSITORIES

1. Export path to packages:

   Note: this path is where the packages for eboa, vboa and the tailored BOA are located.

export PATH_TO_PACKAGES=PATH_TO_PACKAGES

1. Export the UID of the user which will be shared with BOA in the deployment platform:

Note: replace 1003 with the proper ID of the relevant user.

export BOA_UID=1003

1. Export version of BOA deployment (for example 0.1.54):

export VERSION=0.1.54

1. Generate the BOA image:

   Note: replace s2boa and s2vboa references by the relevant names of the tailored BOA

$PATH_TO_RESOURCES/vboa/generate_docker_image_from_pkgs.sh -d $PATH_TO_RESOURCES/vboa/Dockerfile -p $PATH_TO_PACKAGES -o $PATH_TO_RESOURCES/orc_minarc -a s2vboa -l $VERSION -u $BOA_UID -g

Once it is finished, you will see an output like the following containing the path to the docker image:

BOA image exported in: /tmp/tmp.Pq9kQYgh3L/boa.tar
Removing temporal docker container and image
boa_app
boa_app
Untagged: boa:latest
Deleted: sha256:c8de418a20e34f60e84e50eaf827941550846879f8e8fc97bccc9a901b42c15e
Untagged: boa:0.1.54
Deleted: sha256:fe2865914a383dc1932136ae51c2972f0f49441e3409b74360bab28ff57e6398