SBN

Scale up your enterprise with Docker Subdomain Routing

Docker is an open source platform that came to life in 2014 and was recently rated the most loved/wanted tool by developers according to a StackExchange survey. But it’s not just developer preference. In the last two years, the percentage of enterprises with more than half of their containers running in production has increased by 32% (source)

As teams expand their use of Docker for more and higher priority workloads, managing a growing list of hosts becomes a daunting task.

Efficiency and scalability for the masses

To improve ease of use and administration, Sonatype Nexus Repository Pro has added subdomain connectors for Docker users. Where normally unique Docker instances are given a separate port number, now they have a standard name.

By default, listings like the one below that must be shared, remembered, and referenced:

servername.com:996 Jenkins1
servername.com:997 Roman1
servername.com:998 Fileserv1

Developers and system administrators alike know how difficult the various port numbers can be difficult to track and maintain. Instead, what if you could make them easy-to-remember named addresses?

Jenkins1.servername.com
Roman1.servername.com
Fileserv1.servername.com

 

Other benefits include:

  • Improved scalability for more Docker repositories 

  • Avoid misconfiguration risks and delays

  • Avoid modifying config files every time you add a new Docker instance, as with a “reverse proxy” setup

Screenshot of Nexus Repo Manager with Subdomain Routing enabled

Screenshot of Nexus Repo Manager with Subdomain Routing enabled

For more information, see the project documentation.

Related 

*** This is a Security Bloggers Network syndicated blog from Sonatype Blog authored by Chris Good. Read the original post at: https://blog.sonatype.com/scale-up-your-enterprise-with-docker-subdomain-routing