Skip to content

Commit 4fee2e7

Browse files
committed
Clarify image compatibility artifact creation
Signed-off-by: Marcin Franczyk <[email protected]>
1 parent 041fff3 commit 4fee2e7

File tree

1 file changed

+4
-2
lines changed
  • content/en/blog/_posts/image-compatibility-in-cloud-native-environments

1 file changed

+4
-2
lines changed

content/en/blog/_posts/image-compatibility-in-cloud-native-environments/index.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -126,8 +126,10 @@ The previous compatibility specification example in this article exemplified thi
126126
127127
2. **Attach the artifact to the image**
128128
The image compatibility specification is stored as an OCI artifact.
129-
Using the [oras](https://oras.land/) tool, you can attach this metadata to your container image.
130-
This can be done with the following command:
129+
You can attach this metadata to your container image using the [oras](https://oras.land/) tool.
130+
The registry only needs to support OCI artifacts, support for arbitrary types is not required.
131+
Keep in mind that the container image and the artifact must be stored in the same registry.
132+
Use the following command to attach the artifact to the image:
131133
132134
```bash
133135
oras attach \

0 commit comments

Comments
 (0)