Installing

Updated on May 26, 2026

Running as a Container

With persistent storage:

docker run -p 5000:5000 \
  -v "olareg-data:/home/appuser/registry" \
  ghcr.io/olareg/olareg serve --dir /home/appuser/registry

For an ephemeral registry:

docker run -p 5000:5000 --rm \
  ghcr.io/olareg/olareg serve --store-type mem

Installing as a Binary

Binaries can be downloaded from the releases page.

Downloading the latest release for linux/amd64 can be done with curl:

curl -L https://github.com/olareg/olareg/releases/latest/download/olareg-linux-amd64 >olareg
chmod 755 olareg

For binaries downloaded on MacOS, the quarantine attribute can be removed with:

xattr -d com.apple.quarantine olareg

Using in Go Unit Tests

One of the goals of olareg was to serve as a simple registry implementation to test tooling that works with container registries. Integrating it into unit tests with the httptest based server involves the following setup:

func TestMethod(t *testing.T) {
	rh := olareg.New(config.Config{
		Storage: config.ConfigStorage{
			StoreType: config.StoreMem,
			RootDir:   "./testdata", // serve content from testdata, writes only apply to memory
		},
	})
	ts := httptest.NewServer(rh)
	t.Cleanup(func() {
		ts.Close()
		_ = rh.Close()
	})
	tsURL, err := url.Parse(ts.URL)
	if err != nil {
		t.Fatal("failed to parse url %s: %v", ts.URL, err)
	}
	// send requests to tsURL.Host registry server ...
}

Go docs may be found at https://pkg.go.dev/github.com/olareg/olareg.

Verifying Signatures

Binaries and images have been signed with cosign.

For images:

cosign verify \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --certificate-identity-regexp https://github.com/olareg/olareg/.github/workflows/ \
  ghcr.io/olareg/olareg:latest

For binaries:

cmd=olareg
arch=linux-amd64
curl -L https://github.com/olareg/olareg/releases/latest/download/${cmd}-${arch} >${cmd}
chmod 755 olareg
curl -L https://github.com/olareg/olareg/releases/latest/download/${cmd}-${arch}.pem >${cmd}-${arch}.pem
curl -L https://github.com/olareg/olareg/releases/latest/download/${cmd}-${arch}.sig >${cmd}-${arch}.sig
cosign verify-blob \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --certificate-identity-regexp https://github.com/olareg/olareg/.github/workflows/ \
  --certificate ${cmd}-${arch}.pem \
  --signature ${cmd}-${arch}.sig \
  olareg
rm ${cmd}-${arch}.pem ${cmd}-${arch}.sig

Starting in olareg v0.1.3, signatures are also provided using sigstore bundles. To facilitate the migration to bundles, the previous signatures will still be distributed for several releases and a deprecation notice will be provided in the release notes. To verify signatures using the sigstore bundles, use the following commands:

cmd=olareg
arch=linux-amd64
curl -L https://github.com/olareg/olareg/releases/latest/download/${cmd}-${arch} >${cmd}
chmod 755 ${cmd}
curl -L https://github.com/olareg/olareg/releases/latest/download/${cmd}-${arch}.sigstore.json >${cmd}-${arch}.sigstore.json
cosign verify-blob \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --certificate-identity-regexp https://github.com/olareg/olareg/.github/workflows/ \
  --bundle ${cmd}-${arch}.sigstore.json \
  ${cmd}
rm ${cmd}-${arch}.sigstore.json

Next Steps

Authentication and Authorization should be configured on any publicly facing installs that aren’t read-only.
CLI Options detail how to configure the application (this are also available from the --help CLI flag).