The Docker.io team has been working hard on a number of new services and we’re excited to roll them out to you today. With this release, we aspired to provide services to help users share repos with others, drill-down into repo contents, and automate and link workflows.
One of the most-requested features is private repos. Say you’re working on a project that you want to share with the world but is not yet ready for prime time. Now you can push your work-in-progress to a private repo on docker.io and invite only specific collaborators to pull from and push to it. When you’re ready, you can make your private repo public, and it’ll automatically be indexed and publicly searchable.
All services on Docker.io to this point have been freely available, and we feel this is important in fostering an active, growing community around Docker. For this reason, most of Docker.io’s services will continue to be free but, as Ben has already publicly shared, to support continued investment in Docker we will over time offer optional pay-for services.
Private repos is the first example of this. Specifically, we will continue to offer users an unlimited number of public repos, but the ability to make them private will be a pay-for service. We endeavored to keep the cost within range of a small team’s budget, and pricing starts at $7 per month for 5 private repos. Check-out private repos here.
To make it easier to work with repos, another new feature is the ability to browse a repo by its image tags and visually inspect the changes within each layer.
In addition to making it easier to share and understand the content of repos, this latest release also provides new features to automate repo-based workflows.
First up are webhooks. Using webhooks, a successful repo push can automatically trigger RESTful notifications to other applications. Next up, to automate Trusted Build workflows we’re rolling out triggers and links. Triggers give you a way to kick-off a Trusted Build with a simple POST to an endpoint. For example, with triggers enabled the owner of a Trusted Build repo can kick-off its build like so:
$ curl --data "build=true" -X POST https://index.docker.io/u/samalba/docker-registry/trigger/b2562468-aea0-11e3-a39e-b6db5999dfec/
Links give you a way to automatically trigger Trusted Builds by syncing the state of your Trusted Build repo with the state of another. So any update to the linked repo automatically kicks-off an update of your Trusted Build repo.
Finally, with all the activity happening on the docker.io service we thought it useful to have a means of selecting events to be pushed to you rather than having to hunt around for status. For that, we’re pleased to announce a new notifications service, found under User Settings > Notifications. In this inaugural release you can select to be notified via email of any of the following events:
The failure of a Trusted Build
Another user stars one of your repos
Another user makes a comment on one of your repos
That’s a lot for one release, and over the coming weeks we’ll be drilling-down into the individual new services and providing more details and examples. How could we make Docker.io more useful for you? We’re eager to hear what you think!
- The Docker.io team
Q: I have a LOT of repos I’d like to make private; what are the pricing tiers?
A: Private repo pricing scales with the number of repos (details here):
Q: What if I make half my private repos public; do I still have to pay for all of them?
A: You may change your pricing tier at any time.
Q: What forms of payment do you accept for private repos?
A: We accept Visa, MasterCard, Discovery, and American Express credit cards.
Q: I’d really like the notifications service to notify me when XYZ event happens; when are you going to support this?
A: We really want to hear feature requests! Please email any and all ideas to firstname.lastname@example.org.