Multi-Architecture Container Images: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
=Internal= | =Internal= | ||
* [[Docker_Concepts#Multi-Architecture_Container_Image|Docker Concepts]] | * [[Docker_Concepts#Multi-Architecture_Container_Image|Docker Concepts]] | ||
=Overview= | |||
A Docker image is represented by a manifest, which is JSON-encoded content representing the image's layers, the corresponding size, the hash of the image, etc. For more details, see: {{Internal|Docker_Concepts#Image|Docker_Concepts | Image}} | |||
Revision as of 01:55, 13 June 2023
External
- https://cloud.google.com/kubernetes-engine/docs/how-to/build-multi-arch-for-arm
- https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/
- https://cloud.google.com/kubernetes-engine/docs/tutorials/migrate-x86-to-multi-arch-arm
Internal
Overview
A Docker image is represented by a manifest, which is JSON-encoded content representing the image's layers, the corresponding size, the hash of the image, etc. For more details, see: