IBM Spectrum Conductor for Containers is now IBM Cloud private!
All applicable references to IBM Spectrum Conductor for Containers will be replaced with IBM Cloud private as soon as possible.
What is IBM Cloud private?
IBM Cloud private is an application platform for developing and managing on-premises, containerized applications. It is an integrated environment for managing containers that includes the container orchestrator Kubernetes, a private image repository, a management console, and monitoring frameworks.
IBM Cloud private-ce (Community Edition) delivers a customer-managed container solution for enterprises. IBM also offers managed container services in the cloud. For more information about IBM-managed container offerings, see IBM Containers website.
For additional information about IBM Cloud private-ce, visit the IBM Cloud private community page.
The supported tags stand for
<IBM Cloud private-ce version>. The
latest tag installs Version 1.2.0.
Supported Docker versions
- Make sure your Docker Engine has a compatible Linux kernel.
Docker 1.12.0 or a later releaseon either Ubuntu Docker Engine or Boot2Docker.
This image was tested on Docker version 1.12.0
Before you begin
- Review the System Requirements.
- Ensure that you complete all the prerequisites for setting up your cluster. For more information about prerequisites, see Preparing your cluster for installation.
- Bookmark the link to the full IBM Cloud private user documentation.
Download the installer image
To download the IBM Cloud private-ce installer, run the following command:
docker pull ibmcom/cfc-installer:1.2.0
To extract the configuration files, run the following command.
docker run -e LICENSE=accept --rm -v "$(pwd)":/data ibmcom/cfc-installer:1.2.0 cp -r cluster /data
cluster directory is created inside your installation directory. For example, if your installation directory is
/opt/cluster folder is created. The
cluster directory contains the following files:
ssh_key- A placeholder file for the SSH private key that is used to communicate with other nodes in the cluster.
hosts- The definition of the nodes in your cluster. See Hosts file.
config.yaml- The configuration settings that are used to install IBM Cloud private-ce to your cluster. See Cluster configuration settings.
misc/ldap/keystone.ldap.conf- A file that defines the integration between the Keystone servers on each master node and your LDAP server.
Modify the configuration files
From the cluster directory, modify the configuration file to match your environment.
Add the IP address of each node in the cluster to the
/cluster/hostsfile. See Hosts file.
OPTIONAL: Overwrite the SSH file with the private key for your cluster. See Sharing SSH keys among cluster nodes
Deploy your environment
You must run this command from the
cluster folder inside your installation directory. If your installation directory is the
/opt/ibm-cloud-private-ce-1.2.0 folder, run the command from the
To deploy your cluster, run the following command:
docker run -e LICENSE=accept --net=host --rm -t -v "$(pwd)":/installer/cluster ibmcom/cfc-installer:1.2.0 install
Verify the status of your installation.
- If the installation succeeded, the access information for your cluster is displayed.
- If you encounter errors during installation, review the Troubleshooting section of the user documentation.
Back up the boot node. Copy your
clusterdirectory to a more secure location.
Access your cluster
From a web browser, navigate to the URL for your cluster. For more information about supported browsers, see Supported browsers.
The Programs listed below are licensed under the following License Information terms and conditions in addition to the Program license terms previously agreed to by Client and IBM. If Client does not have previously agreed to license terms in effect for the Program, the International License Agreement for Non-Warranted Programs (Z125-5589-05) applies.
Program Name (Program Number): IBM Cloud private-ce 1.2 (Community)
The following standard terms apply to Licensee's use of the Program.
Source Components and Sample Materials
The Program may include some components in source code form ("Source Components") and other materials identified as Sample Materials. Licensee may copy and modify Source Components and Sample Materials for internal use only provided such use is within the limits of the license rights under this Agreement, provided however that Licensee may not alter or delete any copyright information or notices contained in the Source Components or Sample Materials. IBM provides the Source Components and Sample Materials without obligation of support and "AS IS", WITH NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTY OF TITLE, NON-INFRINGEMENT OR NON-INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Technology Preview Code
Technology Preview Code (TPC) may be included or distributed with the Program or updates to it but are not part of the Program. TPC is licensed under the same terms as the Program, except as provided below. TPC will be identified as such in the Notices File (or in an updated Notices File accompanying the updates). Some or all of the TPC may not be made generally available by IBM as or in a product. Licensee is permitted to use TPC only for internal use for evaluation purposes and not for use in a production environment. The Notices File may limit this evaluation use to an evaluation period. If so, at the end of such evaluation period Licensee must cease using and uninstall the TPC. IBM provides the TPC without obligation of support and "AS IS," WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE WARRANTY OF TITLE, NON-INFRINGEMENT OR NON-INTERFERENCE AND ANY IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Licensee may not transfer TPC to another party except as a transfer accompanying the Program. TPC may contain a disabling device that will prevent it from being used after the evaluation period ends. Licensee will not tamper with this disabling device or the TPC. Licensee should take precautions to avoid any loss of data that might result when the TPC can no longer be used.
Export and Import Restrictions
This Program may contain cryptography. Transfer to, or use by, users of the Program may be prohibited or subject to export or import laws, regulations or policies, including those of the United States Export Administration Regulations. Licensee assumes all responsibility for complying with all applicable laws, regulations, and policies regarding the export, import, or use of this Program, including but not limited to, U.S. restrictions on exports or reexports. To obtain the export classification of this Program refer to: https://www.ibm.com/products/exporting/.
Separately Licensed Code
The provisions of this paragraph do not apply to the extent they are held to be invalid or unenforceable under the law that governs this license. Each of the components listed below is considered "Separately Licensed Code". IBM Separately Licensed Code is licensed to Licensee under the terms of the applicable third party license agreement(s) set forth in the NON_IBM_LICENSE file(s) that accompanies the Program. Notwithstanding any of the terms in the Agreement, or any other agreement Licensee may have with IBM, the terms of such third party license agreement(s) governs Licensee's use of all Separately Licensed Code unless otherwise noted below.
Future Program updates or fixes may contain additional Separately Licensed Code. Such additional Separately Licensed Code and related licenses are listed in another NON_IBM_LICENSE file that accompanies the Program update or fix. Licensee acknowledges that Licensee has read and agrees to the license agreements contained in the NON_IBM_LICENSE file(s). If Licensee does not agree to the terms of these third party license agreements, Licensee may not use the Separately Licensed Code.
For Programs acquired under the International Program License Agreement ("IPLA") or International Program License Agreement for Non Warranted Program ("ILAN") and Licensee is the original licensee of the Program, if Licensee does not agree with the third party license agreements, Licensee may return the Program in accordance with the terms of, and within the specified time frames stated in, the "Money-back Guarantee" section of the IPLA or ILAN IBM Agreement.
Note: Notwithstanding any of the terms in the third party license agreement, the Agreement, or any other agreement Licensee may have with IBM:
(a) IBM provides this Separately Licensed Code to Licensee WITHOUT WARRANTIES OF ANY KIND;
(b) IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF TITLE, NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SEPARATELY LICENSED CODE;
(c) IBM is not liable to Licensee, and will not defend, indemnify, or hold Licensee harmless for any claims arising from or related to the Separately Licensed Code; and
(d) IBM is not liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages including, but not limited to, lost data, lost savings, and lost profits, with respect to the Separately Licensed Code.
Notwithstanding these exclusions, in Germany and Austria, IBM's warranty and liability for the Separately Licensed Code is governed only by the respective terms applicable for Germany and Austria in IBM license agreements.
Note: IBM may provide limited support for some Separately Licensed Code. If such support is available, the details and any additional terms related to such support will be set forth in the License Information document.
For any license-related inquiries, please contact us at firstname.lastname@example.org.
For more information, please visit: IBM Cloud private] community
- Join us on slack. Click here to receive an invite to our slack community
- Email us at: email@example.com
I had to install python
apt install python
apt install python-pip
pip install docker-py