Push image to Container Registry
Tag with resolved registry id then push; avoids hardcoding the cr.yandex/<reg-id>
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
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>")"'; doneEnumerate every tag across all repos; useful before a registry GC sweep
-
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 4Roll out a new revision from a CR image; note: concurrency caps in-flight requests per instance
-
yc logging read --group-name <name> --since 1h --levels ERROR,WARN --format json | jq -r '.[] | "\(.timestamp) \(.level) \(.message)"'Tail YC Cloud Logging filtered to ERROR/WARN; modern: --since accepts 1h/30m relative windows
-
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 managed wildcard cert then check status; note: needs DNS/HTTP validation to issue
-
yc config set folder-id <id> && yc config listSet default folder-id for the active profile; verify with config list