Skip to content

Application Signing

This section assumes you are signing for development purposes. Signing for production with a vendor private key is not covered.

Important

Before you attempt to load a signed application, you must install a developers license on your HCC2.

Prerequisites

The following prerequisites must be met to sign and subsequently deploy a custom application to an HCC2.

  1. A valid developer's license is installed on the HCC2.

  2. A developer private key is available and is installed in:

    ~/hcc2devtools/menderkeys/

  3. The actions of the Container Preparation step are completed successfully.

  4. The application .yml file is copied to the hcc2devtools folder.

Your <<app-name>>-docker-compose.yml file from the Container Preparation step is completed successfully and the container in your Docker repository is valid.

Packaging and Signing

With the prerequisites met, use your development machine to

  1. Navigate to your hcc2devtools folder.

  2. Execute the packaging script, passing your application yml file. For example:

./package_app.sh <<app-name>>-docker-compose.yml

Warning

You MUST execute this script from the hcc2devtools folder, because it needs access to the private key in the 'menderkeys' sub folder to sign the package.

This script will create a signed output file.

    3. Rename the signed output file

mv collection-signed-private.mender <<name of your choice>>.mender

Result

The resulting mender file can now be deployed to the HCC2 device.