RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
There are two ways to publish an a new app application in ASMS:
But before publishing the new app into ASMS, you first need to publish the OCI image of your DAC app's OCI image application into a container registry that supports OCI compliant format. How to do that, is explained in next section.
Note If you don't want to test or publish your own new DAC app then you can skip this step and try the already published demo apps in the next section.
We offer 3 ways you as App developer can publish your OCI image in container registry :
You can either publish your oci container image to
There are various tools to copy/upload/fetch oci images.
Depending on the oci registry productDepending on the oci registry provider, there are various login/access credential procedures. We will not explain them all.
The instructions we are providing here below are specific to an amazon s3 OCI registry. And you will need the util programs aws cli tools and skopeo.
Configure your profile, add to ~/.aws/credentials. Obviously you have to provide your own correct credentials:
We provide the instructions for Amazon Elastic Container Registry. The private container registry setup RDK-M DAC team is also such type.
You need to have the following util programs installed: aws cli tools and skopeo.
Assuming your host is linux, configure your aws profile ~/.aws/credentials file as per below
Code Block | ||
---|---|---|
| ||
//Obviously you need to fill in your credentials below iso xxxxx and yyyyy. If you want to use the private OCI container registry from RDK-M, request piotr.serafin@consult.red for credentials
| ||
Code Block | ||
| ||
[s3dacrdk] aws_access_key_id = xxxxx aws_secret_access_key = yyyyyy |
Login, create new container repository and publish the OCI image in there:
Code Block | ||
---|---|---|
| ||
# login into private RDK-M OCI container registry aws --profile s3dacrdk ecr-public get-login-password --region us-east-1 | skopeo login --username AWS --password-stdin public.ecr.aws/a0v6o9z7 # create repo# create repo for your application, in which you can publish different versions, example below creates "cobalt" one for Youtube/cobalt application aws --profile s3dacrdk --region us-east-1 ecr-public create-repository --repository-name cobalt # list repos aws --profile s3dacrdk --region us-east-1 ecr-public describe-repositories # upload image, the -1 ecr-public describe-repositories # The actual command that uploads/publishes your local version of a oci image associated with your application to the RDK-M oci-registry # within repo named "cobalt" with the version tag "latest" standstanding for latest version skopeo copy oci-archive:dac-image-cobalt.tar docker://public.ecr.aws/a0v6o9z7/cobalt:latest ## with following command you can download your oci image (test) from RDK-M registry to your local host skopeo copy docker://public.ecr.aws/a0v6o9z7/cobalt:latest oci:cobalttest |
...