Deploy container on Bluemix
- Go to the Bluemix dashboard for the same organization you logged into above. This is available via Bluemix Dashboard.
- Click on Start Containers and you will be taken to your organization’s Catalog, containing all the public and private images stored for your organization.You have not pushed any images to your private registry, so you should only see the following images:
ibm-mobilefirst-starter– Starter image for IBM MobileFirst Platform Foundation
ibm-node-strong-pm– Starter image for IBM Strongloop Process Manager
ibmliberty– IBM-Supported WebSphere Liberty Profile runtime container image
ibmnode– IBM-Supported Node.js runtime container image
- Select the
ibmlibertyimage from the list of available images.
- You are taken to the Create Container page.This is a user-interface driven method to deploying container instances on IBM Containers. The same capability is available through the CLI, but you will be using the UI to deploy your first container on IBM Bluemix.
- Choose the space in your organization where you would like to host the container. At this point, you should probably only have the
BAO-TWspace.Select BAO-TW.In Bluemix, spaces provide a mechanism to collect related applications, services, containers, and the users that can collaborate on the resources. You can have one or more spaces within an organization.
- Provide a name for the container.Enter
libertydemo1. This is the same as the
--nameparameter when using the Docker CLI.
- Choose the size of the container.Select Pico (64 MB Memory, 4 GB Storage). IBM Containers allows you to select right-sized hardware resources for your container instances to allow for cost-effective runtimes. Note: The size of a container cannot be changed once it has been created.
- Associate a publicly-routed IP address to the newly created container.Select the option Request and bind a public IP. or your existed public IPIn Bluemix, you are provided with a default private network for all your running container instances automatically. You can optionally select container instances to be assigned Public IP addresses and expose them to the public internet. This is useful for web frontends and load balancing containers, while your database and similarly functioning containers can remain walled off from public internet traffic.
- When deploying through the Bluemix user interface, container images have their exposed ports automatically detected. You should see the following ports automatically detected when viewing the
ibmlibertyimage: 22/tcp, 9080/tcp, 9443/tcp
- Click CREATE.Your container instance will now be deployed to Bluemix. You will be redirected to the dashboard overview for this new container instance.In future tasks and labs you will interact with elements under the Advanced Options and Vulnerability Assessment, but feel free to explore before clicking CREATE. These additional options allow you to work with volumes stored on Bluemix, bind your containers to over 150 Bluemix services, and inject your own SSH key into each container you deploy.
- From the dashboard overview, you should see the Public IP address assigned to your running WebSphere Liberty container.Find your Public IP address and enter it into a browser, like http://Public_IP_Address:9080. You should be presented with the Welcome to Liberty landing page.Alternatively, you can click on the 9080 port that is linked from the dashboard page to open the container instance via the exposed port. You should see the same Welcome to Liberty landing page.
- Back in the dashboard overview page in Bluemix, you are presented with all the controls necessary to manage your container instance. You are also presented with pre-integrated Logging & Monitoring for all your container instances.Click on Monitoring and Logs on the left hand menu and you will be taken to deeper view into the provided monitoring & logging stack. You can configure your containers to log additional information directly to this endpoint as well.This is a key piece in enabling container-based infrastructures, as it becomes quickly unmanageable to interact with all the singular instances at the lowest level. This is just one of a few capabilities that IBM Containers provides to reduce the amount of time users take to get value out of Docker containers and hosted infrastructure. You’ll touch on a few more in subsequent labs.
- Once you have verified your container was successfully deployed, you can delete your running container instance via the DELETE button on the container dashboard.As you are most likely on a Trial account, removing containers after each lab will make sure you are making efficient use of your Trial quota.