I'd like to propose a new remote resolver named "filesystem", which allows pulling (and pushing) OCI images from a filesystem.
Filesystem is expected to be a local filesystem, but can be arbitrary network filesystems (e.g. NFS, S3 on FUSE, IPFS on FUSE...)
PR
PR is almost ready, but didn't open yet because this seems to require technical discussion.
master...AkihiroSuda:resolver-filesystem.20170510
Currently, OCI 1.0.0-rc5 is supported via my generic OCI image manipulation library (https://github.com/AkihiroSuda/filegrain/tree/master/image)
Example
$ ls /foo/bar
oci-layout
index.json
...
$ dist pull --resolver filesystem localhost/foo/bar:latest
Concern
- Since current resolver interface requires "hostname" part, the filesystem resolver always requires
localhost/ prefix. This might be weird.
I'd like to propose a new remote resolver named "filesystem", which allows pulling (and pushing) OCI images from a filesystem.
Filesystem is expected to be a local filesystem, but can be arbitrary network filesystems (e.g. NFS, S3 on FUSE, IPFS on FUSE...)
PR
PR is almost ready, but didn't open yet because this seems to require technical discussion.
master...AkihiroSuda:resolver-filesystem.20170510
Currently, OCI 1.0.0-rc5 is supported via my generic OCI image manipulation library (https://github.com/AkihiroSuda/filegrain/tree/master/image)
Example
Concern
localhost/prefix. This might be weird.