Try it with any public git repo!
$ docker run ctr.run/github.com/undefinedlabs/hello-world:master
We built Ctr.run to stop wasting time and money building, pushing, and storing container images that never get used. To speed up all container builds with automatic caching and parallelism that works everywhere: locally, across CI providers, and container runtimes.
And to eliminate the guesswork of what :tag to pull to see the latest changes in master or a feature-branch.
Using ctr.run is easy, simply
docker run the git commit, branch or tag you need, when you need it:
Automatic build caching
Parallel build step execution
Works with k8s and other container runtimes
docker run ctr.run/github.com/... and ctr.run will automatically build your container image – faster than you ever imagined possible.
ctr.run is built using the most innovative, efficient and fastest container build system in the world: buildkit. Thanks to buildkit, build steps are automatically cached and parallelized, and all builds are incremental by default.
ctr.run uses CDN-based edge caching to guarantee availability and bring you the fastest pulls anywhere around the globe. Take that and rewind it back.
Stop building and pushing images that you'll never use. It's common to build and push to a registry as part of CI, but many of these images rarely get used. ctr.run only builds the container images you'll actually run.
Imagine there's a new commit to try out. It has a Dockerfile, and there's an image in DockerHub, but it's from last week's release, what do you do?
docker run ctr.run/github.com/namespace/repo[:commit-hash, branch-name, tag-name]
Kubernetes ◇ AWS ECS ◇ AWS Fargate ◇ AKS ◇ GKS ◇ Github Actions ◇ Jenkins ◇ CircleCI ◇ Docker for Mac/Windows ◇ Okteto ◇ k3s ◇ OpenShift ◇ Pivotal Cloud Foundry ◇ and everywhere else!