To push a OCI packages to a registry, run:
gdcloud artifacts push SOURCE DESTINATION
To push a single manifest of the repository to the registry, run:
gdcloud artifacts push SOURCE DESTINATION --single-manifest-repo
To push OCI packages to a registry without adhering to TLS protocols, run:
gdcloud artifacts push SOURCE DESTINATION --insecure
The SOURCE path must point to a directory containing the OCI bundle.
The DESTINATION is a reference of a remote OCI image. For example, gcr.io/cloud-marketplace/google/nginx:1.25.
This command writes the extracted image to the output path specified in SOURCE. This output path must point to an empty directory.
선택적 플래그
--ca-cert-path string Absolute file path to the user-provided CA certificate file that is used to push a manifest over a HTTPS connection.
--insecure Allow pushing to the registry, and establish a connection to the server, even for server connections otherwise considered insecure.
--single-manifest-repo Tag and push the single manifest of the repository, as opposed to the image index, to the registry.
GDCLOUD 전체 플래그
이러한 플래그는 모든 명령어에서 사용할 수 있습니다(--configuration, --format, --help, --project, --quiet).
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eThe \u003ccode\u003egdcloud artifacts push\u003c/code\u003e command is used to push OCI packages to a specified registry.\u003c/p\u003e\n"],["\u003cp\u003eThe command requires a source directory containing the OCI bundle and a destination that is a remote OCI image reference.\u003c/p\u003e\n"],["\u003cp\u003eYou can push a single manifest of the repository instead of the image index using the \u003ccode\u003e--single-manifest-repo\u003c/code\u003e flag.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003e--insecure\u003c/code\u003e flag allows pushing to registries and establishing connections to servers, even if considered insecure.\u003c/p\u003e\n"],["\u003cp\u003eA user-provided CA certificate file can be specified via \u003ccode\u003e--ca-cert-path\u003c/code\u003e for pushing over HTTPS connections.\u003c/p\u003e\n"]]],[],null,["# gdcloud artifacts push\n\nNAME\n----\n\ngdcloud artifacts push - Push OCI packages to a registry.\n\nSYNOPSIS\n--------\n\n gdcloud artifacts push SOURCE DESTINATION [flags]\n\n### EXAMPLES\n\n To push a OCI packages to a registry, run:\n\n gdcloud artifacts push SOURCE DESTINATION\n\n To push a single manifest of the repository to the registry, run:\n\n gdcloud artifacts push SOURCE DESTINATION --single-manifest-repo\n\n To push OCI packages to a registry without adhering to TLS protocols, run:\n\n gdcloud artifacts push SOURCE DESTINATION --insecure\n\n The SOURCE path must point to a directory containing the OCI bundle.\n The DESTINATION is a reference of a remote OCI image. For example, gcr.io/cloud-marketplace/google/nginx:1.25.\n This command writes the extracted image to the output path specified in SOURCE. This output path must point to an empty directory.\n\n### OPTIONAL FLAGS\n\n --ca-cert-path string Absolute file path to the user-provided CA certificate file that is used to push a manifest over a HTTPS connection.\n --insecure Allow pushing to the registry, and establish a connection to the server, even for server connections otherwise considered insecure.\n --single-manifest-repo Tag and push the single manifest of the repository, as opposed to the image index, to the registry.\n\n### GDCLOUD WIDE FLAGS\n\nThese flags are available to all commands: `--configuration`, `--format`, `--help`, `--project`, `--quiet`.\n\nFor more information, see the [gdcloud CLI reference overview](/distributed-cloud/hosted/docs/latest/appliance/resources/gdcloud-reference/gdcloud) page."]]
