Stay on Top of Enterprise Technology Trends
Get updates impacting your industry from our GigaOm Research Community
Google Cloud users can now load up their private Docker container images into the search giant’s new Google Container Registry, which Google said Friday is now available in beta and the company noted “is not covered by any SLA or deprecation policy and may be subject to backward-incompatible changes.”
If you are a [company]Google[/company] Cloud customer, your [company]Docker[/company] container images — which contain all the necessary components for spinning up containers, like the source code and binary files — will be “automatically encrypted before they are written to disk,” according to the Google blog post detailing the registry.
From the blog post:
[blockquote person=”Google” attribution=”Google”]Access control: The registry service hosts your private images in Google Cloud Storage under your Google Cloud Platform project. This ensures by default that your private images can only be accessed by members of your project, enabling them to securely push and pull images through the Google Cloud SDK command line. Container host VMs can then access secured images without additional effort.
Google said that with the container images loaded up in the Google cloud and cached in its data centers, users should be able to deploy them to Google Container Engine clusters as well as “Google Compute Engine container-optimized VM’s.”
As for pricing, Google said that while the service is in beta, users “will be charged only for the Google Cloud Storage storage and network egress consumed by your Docker images.”
This seems like part of Google’s strategy to hype up its Google Container Engine, which is the managed-service version of the open-source Kubernetes container-management system. Instead of storing your private containers in the Docker Hub or CoreOS’s Enterprise Registry, Google wants users to trust it with holding on to the valuables.
For now, the Google Container Engine only allows users to craft managed clusters within its system and “It doesn’t have the ability to span across multiple cloud providers,” said Greg DeMichillie, Google’s director of product management for its cloud platform, during the announcement of the container engine last November.