RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
But before publishing the app into ASMS you first need to publish your DAC app's OCI image into a 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 image.
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 will need the aws cli tools and skopeo.
Configure your profile, add to ~/.aws/credentials:
Code Block | ||
---|---|---|
| ||
[s3dacrdk]
aws_access_key_id = xxxxx
aws_secret_access_key = yyyyyy |
Login, create repository and upload 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
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 |
You have to remember the OCI image URL, which in this example is docker://public.ecr.aws/a0v6o9z7/cobalt:latest. You will need it when publishing the DAC app to ASMSTBD...
...