RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
If you don't want to test or publish your own DAC app then you can skip this step and tries trie the already published demo apps in the next section. There are two ways to publish an app in ASMS:
...
But before publishing the app into ASMS you first need to publish your DAC app's OCI image into a container registry that the RDK ASMS can reach. After all, it needs to be able to generate a bundle and thus needs access to this OCI imagesupports OCI compliant format.
...
We offer 3 ways you as App developer can publish your OCI image in container registry :
There are various tools to copy/upload/fetch oci images.
Depending 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 You need a read/write account to some OCI registry which is readable by RDK ASMS cloud service. Once you have that you can upload your OCI image as documented below. Remark: these instructions are specific to an amazon s3 OCI registry. You And you will need the util programs aws cli tools and skopeo.
Configure your profile, add to to ~/.aws/credentials. Obviously you have to provide your own correct credentials:
...
Login, create repository and upload publish the OCI image:
Code Block | ||
---|---|---|
| ||
# login aws --profile s3dacrdk ecr-public get-login-password --region us-east-1 | skopeo login --username AWS --password-stdin public.ecr.aws/a0v6o9z7 # create repo 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 tag "latest" stand for latest version skopeo copy oci-archive:dac-image-cobalt.tar docker://public.ecr.aws/a0v6o9z7/cobalt:latest # download image (test) skopeo copy docker://public.ecr.aws/a0v6o9z7/cobalt:latest oci:cobalttest |
...