Push an image to Container Registry

Tag the image with the registry ID looked up on the fly, then push it, so cr.yandex/<reg-id> is not hardcoded.

docker tag <name>:<id> cr.yandex/$(yc container registry get --name <name> --format json | jq -r .id)/<name>:<id> && docker push cr.yandex/$(yc container registry get --name <name> --format json | jq -r .id)/<name>:<id>

tool
yc32 commands
tags
yccicloud

More yc commands

  • yc container repository list --format json | jq -r '.[].name' | while read r; do yc container image list --repository-name "$r" --format json | jq -r '.[] | "\(.name):\(.tags[]? // "<none>")"'; done

    List every tag in every repository; handy before a registry cleanup.

  • yc serverless container create --name <name>; yc serverless container revision deploy --container-name <name> --image cr.yandex/<id>/<name>:<id> --cores 1 --memory 512M --service-account-id <id> --concurrency 4

    Deploy a new revision from a Container Registry image; --concurrency limits parallel requests per instance.

  • yc logging read --group-name <name> --since 1h --levels ERROR,WARN --format json | jq -r '.[] | "\(.timestamp) \(.level) \(.message)"'

    Read Cloud Logging entries with ERROR and WARN levels only; --since also takes values like 30m.

  • yc certificate-manager certificate request --name <name> --domains <host>,*.<host> && yc certificate-manager certificate list --format json | jq -r '.[] | "\(.name)\t\(.status)\t\(.not_after)"'

    Request a certificate for a domain and its wildcard, then check the status; it is issued only after DNS or HTTP validation.

  • yc config set folder-id <id> && yc config list

    Set the default folder-id for the active profile and check it with config list.

all 32 yc commands