5f71b764fc
older versions of json-iterator appear to have an issue with maps. We are most certainly hitting this panic with maps. https://github.com/anuvu/zot/blob/master/pkg/api/routes.go#L898 On the json-iterator/go side, json-iterator/go@acfec88 json-iterator/go#388 |
||
|---|---|---|
| .bazel | ||
| cmd/zot | ||
| docs | ||
| errors | ||
| examples | ||
| pkg | ||
| test/scripts | ||
| .bazelignore | ||
| .bazelrc | ||
| .gitignore | ||
| .travis.yml | ||
| BUILD.bazel | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| Makefile | ||
| Makefile.bazel | ||
| README.md | ||
| stacker.yaml | ||
| WORKSPACE | ||
| zot.go | ||
zot 
zot is a vendor-neutral OCI image repository server purely based on OCI Distribution Specification.
- Conforms to OCI distribution spec APIs
- Uses OCI storage layout for storage layout
- TLS support
- Authentication via TLS mutual authentication and HTTP BASIC (local htpasswd and LDAP)
- Doesn't require root privileges
- Swagger based documentation
- Can run compliance checks against registries
- Released under Apache 2.0 License
go get -u github.com/anuvu/zot/cmd/zot
Presentations
Build and install binary (using host's toolchain)
go get -u github.com/anuvu/zot/cmd/zot
Full CI/CD Build
- Build inside a container (preferred)
make binary-container
- Alternatively, build inside a container using stacker (preferred)
make binary-stacker
- Build using host's toolchain
make
Build artifacts are in bin/
Serving
bin/zot serve _config-file_
Examples of config files are available in examples/ dir.
Compliance checks
bin/zot compliance -H hostIP -P port [-V "all"] [--json]
Compliance is important for the following reasons:
-
A standards-based client code can be implemented that can then interact with compliant registries.
-
Customers benefit from the ability to move and locate their images across compliant registries.
Methodology
-
A positive compliance means the registry is compliant and meaningful work can be accomplished when interacting with that registry.
-
A negative compliance means the registry is compliant, however, it only returns errors that are compliant and no meaningful work can be performed when interacting with that registry.
The focus of compliance tests is positive compliance.
Compliance Reports
| Registry | Notes |
|---|---|
| zot |
|
| docker |
|
| quay | TBD |
Ecosystem
skopeo
skopeo is a tool to work with remote image repositories.
We have a patched version available that works with zot.
git clone https://github.com/anuvu/skopeo
cd skopeo
make GO111MODULE=on binary-local
cri-o
cri-o is a OCI-based Kubernetes container runtime interface.
We have a patched version of containers/image available that works with zot which must be linked with cri-o.
git clone https://github.com/cri-o/cri-o
cd cri-o
echo 'replace github.com/containers/image => github.com/anuvu/image v1.5.2-0.20190827234748-f71edca6153a' >> go.mod
make bin/crio crio.conf GO111MODULE=on
Caveats
- go 1.12+
- The OCI distribution spec is still WIP, and we try to keep up