Part Two.. Installing team city into Rancher via docker hub
Note : If you’ve reached this page directly, it’s advised to complete part one of tutorial. Part one covers creating the environment needed to begin deployment of your first container. The installation of process of teamcity once running is also not covered.
Although containers can be installed directly onto hosts I’d advise working at the service level. Services allow more advanced rules for provisioning to be applied and generally make day to day activities easier.
The first part of the process is creating a stack. A stack can contain a range of container types and instances.
I called mine “ContinuousIntegration”
This is how eventually how your stack will look. In order to create the server click “Add Service”.
Creating a service looks something like this :
- Give the service a sensible name.
- “Select Image” needs to be set to “aerofs/teamcity”
- Ensure port 8111 is open on both public host and mapped to the private container port.
- In the networking tab ensure a hostname is specified you’ll need this later when adding a build agent.
By default no containers will be provisioned click the “Play” button.
Next click the service name to drill into the service and the finally on the container name.
Finally paste the “Host IP” followed by “:8111” into a browser and if all’s well teamcity should appear.
In the next part I’ll cover provisioning a build agent.