OCI Artifacts as Files: A Look Behind the ORAS File System
An application wants to read a file. However, the file is not located on a hard drive but exists as an artifact in an OCI registry. Does the application therefore need to know how to resolve manifests, query tags, and download blobs?
This is exactly where the ORAS filesystem comes in: It translates the world of OCI artifacts into the familiar interfaces of Java NIO. From a developer’s perspective, the boundary between these two worlds is particularly interesting. A path can be constructed relatively easily. Mapping a remote, content-addressed artifact in such a way that file access remains meaningful requires significantly more decision-making.