Getting started with IBM Containers on Bluemix using the UI

Share: Share on FacebookTweet about this on TwitterShare on Google+Share on LinkedInShare on RedditEmail this to someonePrint this page

Now that you’ve learned about the top five game-changing capabilities of IBM Containers on Bluemix, it is important to leverage the free trial and get started today.

1. Log into the Bluemix, navigate to the “Dashboard”, and select “IBM Containers”.


2. You can either view documentation or sample labs or select “Create a Container”.


3. The deployment panel offers a variety of configuration parameters.

  • Select an image from the registry (i.e., ibmliberty).  By default, your private registry is populated with a few IBM images and you can upload any Docker image to your registry to run on the Bluemix cloud.
  • Provide a meaningful name for the container or group (i.e., liberty1).
  • Specify the container size for your workload.  Each size has a defined amount of memory and local storage for the container.
  • Either deploy a single container or a scalable group of containers.  A single container is great for testing or a simple workload.  A group deployment includes a load balancer to route incoming requests to the containers within that group and the group can be scaled based on workload.
    • Single container:
      • Assign a public IP address if you need your container to be accessible by others (alternatively you can assign a public IP at a later time).
      • Specify the ports that are public for your application (i.e., 80/443 for web).
      • Optionally assign an ssh key to the container to configure a trusted connection to your new container.
    • Container groups:
      • A group is beneficial to deploy multiple copies of the same image and configure load balancing for flexibility in adapting to various workloads.
      • Specify the number of instances (Note: you can increase or decrease the number of running containers later).
      • Optionally, change the “Route domain” from “Leave unassigned” to “” and then enter the host name entry for this deployment (Note: the domain name must be unique for this domain, but we’ll check for you).
      • Specify the port that will field incoming requests.
      • Optionally, select the “Auto-recovery” to automatically deploy a new container if one in the group crashes.  This is a great way to ensure you maintain the desired number of running instances.
  • Click Next.


4. Review your previous selections.

  • If your container or group of containers requires persistent data, you can add a volume and specify the mount point on your container(s).
  • Additionally, you can bind any existing Bluemix (Cloud Foundry) app that is running.
  • Click “Deploy”.



5. On the dashboard, you can monitor and manage the newly deployed container(s).

  • Each container or group of containers provides detailed information about that deployment:
    • Private and Public IP address
    • Allocated resources
    • CPU, memory, and network utilization metrics
  • Container management allows you to stop, pause, restart, or delete instances


Be sure to start your FREE trial today!


What are your container use cases, concerns or issues? Check out IBM Bluemix today! Let’s continue the discussion in the comments below, or you can follow me on Twitter @ChrisRosen188.


Share: Share on FacebookTweet about this on TwitterShare on Google+Share on LinkedInShare on RedditEmail this to someonePrint this page
Chris Rosen
Chris Rosen is a Technical Product Manager for IBM Containers within IBM Cloud Business Unit. With over fifteen years’ experience, he has held a variety of roles within the organization. Currently, Chris is responsible for interfacing with development and design teams for IBM Bluemix, gathering and understanding customer requirements, and determining future product plans. He has a Bachelor of Science in Information Technology and a Masters of Business Administration, both from Rochester Institute of Technology. Chris also holds certifications for MCSA, MCSE, CCNA, ITIL, and OpenGroup IT Specialist.
Chris Rosen