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 survey. But it's not just developer preference. In the last two years, the percentage of enterprises with more than half of their containers in production has increased by 32%.
As teams expand their use of Docker for more and higher priority workloads, managing a growing list of hosts becomes a daunting task.
To improve ease of use and administration, Sonatype Nexus Repository 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 must be shared, remembered, and referenced:
| nexus.example.com:1996 | Jenkins |
| nexus.example.com:1997 | Roman |
| nexus.example.com:1998 | Fileserv |
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?
| Jenkins.nexus.example.com |
| Roman.nexus.example.com |
| Fileserv.nexus.example.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 Sonatype Nexus Repository with Subdomain Routing enabled
For more information, see the project documentation or our infographic summary: