Page History

...

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.

Publish the OCI image

...

in OCI registry

We offer 3 ways you as App developer can publish your OCI image in container registry :

• You can publish your container image to any of public accessible OCI container registries on the internet. Requirement is that the registry supports OCI container format, the container is uploaded & stored there in the OCIcontainer image format (so not in docker format) and is fetchable/accessible (read only, without any user/login) from RDK DAC cloud system.
• You can upload your OCI image to the private OCI registry "public.ecr.aws/a0v6o9z7" hosted as part of RDK DAC cloud. Procedure further detailed below. For that you do need to have/request an account & credentials for this registry, via email to Piotr Serafin  or bcatrysse@libertylgobal.com. (When there is time/money this should be improved and setup as part of registering as New Application maintainer in RDK DAC cloud system or Firebolt Connect system)
• You can ask someone from RDK-M DAC cloud support team (who TBD, ad interim Piotr S or Stefan V or BartC ) to create repo associated with your app in this above registry and upload your provided OCI image there for version you specified

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:

# 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

...