Container Registry
Your builds get direct access to your private container registry at nscr.io. This seamless integration eliminates the complexity of registry authentication while providing enterprise-grade performance and global availability.
From Namespace instances
No configuration changes required
When running your CI on Namespace, access to nscr.io is already configured. Each Namespace workload embeds short-lived credentials that grant direct access to the container registry.
$ docker pull nscr.io/<workspace-id>/app:latestYour workspace identifier can be found in the Dashboard.
Local Docker integration
Using the CLI, you can also configure your local Docker to access nscr.io.
Configure your Docker
$ nsc docker loginThe command above will update your local Docker configuration and print your container registry address (e.g. nscr.io/8enum0hp1l5ii).
If you want to obtain the address without updating your Docker configuration, run nsc workspace describe.
Build and push
$ docker build . -t nscr.io/8enum0hp1l5ii/app:latest --pushObservability
Our Dashboard provides a holistic overview over the images that you have pushed to nscr.io. You can understand access patterns per tag, and the evolution of image sizes over time.
When looking at a single image tag, you can see the historic versions, and which are still being pulled today. For multi-platform images, you can also understand how much each platform contributes to the combined image size.
Build and Push in One Command
When doing quick image iterations, our CLI offers a simple command to build and push an image without reconfiguring your local Docker client.
Build and push
$ nsc build . --name app --pushThat's it! With a single command, you've built an image using a high-performance, remote builder and pushed it to nscr.io.
Access Controls
Images pushed to nscr.io are shared with your workspace by default, allowing for frictionless collaboration. Namespace supports fine-grained access controls, allowing you to flexibly restrict or grant image access.