1
0
Fork 0
mirror of https://github.com/imjasonh/kontain.me synced 2026-07-07 00:32:28 +00:00
No description
Find a file
dependabot[bot] d8b66508ad
Bump github.com/sigstore/rekor from 1.5.1 to 1.5.2
Bumps [github.com/sigstore/rekor](https://github.com/sigstore/rekor) from 1.5.1 to 1.5.2.
- [Release notes](https://github.com/sigstore/rekor/releases)
- [Changelog](https://github.com/sigstore/rekor/blob/main/CHANGELOG.md)
- [Commits](https://github.com/sigstore/rekor/compare/v1.5.1...v1.5.2)

---
updated-dependencies:
- dependency-name: github.com/sigstore/rekor
  dependency-version: 1.5.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-06-30 12:21:14 +00:00
.github update deps 2026-05-12 09:09:26 -04:00
cmd git: document incremental plan/blockers; some deps work 2026-05-15 10:30:35 -04:00
internal fix upload-pack negotiation for stateless-RPC 2026-05-13 21:54:40 -04:00
pkg readme: links to oci.dag.dev 2026-05-14 11:21:27 -04:00
.gitignore deploy using terraform 2023-04-25 10:56:19 -04:00
.terraform.lock.hcl update deps 2026-05-12 09:09:26 -04:00
apps.tf tweak resources 2026-05-14 11:32:11 -04:00
go.mod Bump github.com/sigstore/rekor from 1.5.1 to 1.5.2 2026-06-30 12:21:14 +00:00
go.sum Bump github.com/sigstore/rekor from 1.5.1 to 1.5.2 2026-06-30 12:21:14 +00:00
LICENSE Use ko to build, add LICENSE headers 2018-12-08 17:56:33 -05:00
main.tf put the train back on its rails 2025-02-14 03:52:52 -06:00
prober.tf put the train back on its rails 2025-02-14 03:52:52 -06:00
README.md readme: links to oci.dag.dev 2026-05-14 11:21:27 -04:00

kontain.me

CI Deploy

Serving container images generated on-demand, at the time they are requested.

These include:

This repo also serves a few non-registry oddities:

Caveats

  • The registry does not accept pushes.
  • This is a silly hack and probably isn't stable. Don't rely on it for anything serious.
  • It could probably do a lot of smart things to be a lot faster. 🤷
  • Blobs and manifests are cached for 24 hours wherever possible, but will be rebuilt from scratch after that time.

How it works

The service is built on Google Cloud Run.

When the service receives a request for an image manifest, it parses the request and generates layers for the requested image, writing the manifest and blobs to Google Cloud Storage. After it receives the manifest, docker pull fetches the blobs. The app simply redirects to Cloud Storage to serve manifests and blobs.