SupportConsoleDevelopersStart a trialContact

3.2. Creating a Root Container

Abstract

A creating a root container involves using SSH to log into a remote host, downloading the required binaries from a Maven repository, and installing the container on the host.

Overview

Creating a remote root container installs a new Fuse container on a remote host using SSH. The management console will attempt to establish an SSH connection with the remote host using the provided user credentials. Once it is connected it will run a script that downloads the binary files required to install a Fuse container, installs the container in the user's home folder, starts the container, and provisions all of the specified profiles.
In order for this action to work the remote host must have SSH installed and active. The specified user must also have permissions to install the required files on the host's file system.
Important
You cannot install remote root containers on Windows machines using the management console.

Procedure

To create a remote root container:
  1. Select Containers from the main menu.
    The Containers page opens.
  2. Click Create Fuse Container.
    The Create Fuse Container page opens.
  3. In the Name field, enter a name for the new container.
  4. If you want to make the new container a registry server check Make container a distributed registry server.
    Important
    It is recommended that if you create a registry server that you do not deploy any other services into the container.
  5. If you want to pass any special flags to the container's JVM:
    1. Check JVM Options.
    2. Enter the options to pass to the JVM in the field next to the check box.
  6. If you need to use a Maven proxy to access the repository containing your Fuse artifacts, check the Maven Proxy URL field and enter the URL for your Maven proxy.
  7. If you want to create multiple instances of the container, enter a number greater than one in the Count field.
    When you create multiple containers the container's number is appended to the value specified in the Name field.
  8. Select how the container will report its IP address to other containers from the options in the Resolver drop-down list.
    The options are:
    Local Hostname
    When a requests for the container's location are made, the container's local hostname is returned.
    Local IP
    When a requests for the container's location are made, the container's local IP address is returned.
    Public Hostname
    When a requests for the container's location are made, the container's public hostname address is returned.
    Public IP
    When a requests for the container's location are made, the container's public IP address is returned.
  9. Click Next.
    The Select profiles to install on the container page opens.
  10. Select the version of profiles you want to use for provisioning the container.
    The value of this drop down defaults to the value set on the Profiles page.
  11. Select one or more profiles to deploy to the container.
  12. Click Next.
    The Select the type of container page opens.
  13. Select Remote root container.
  14. Click Next.
    The SSH Server Configuration page opens.
  15. In the Hostname field, enter the DNS name, or IP address, for the host onto which the container will be deployed.
  16. If your SSH configuration doesn't use the default port, enter the proper port in the Port field.
  17. In the Username field, enter the name of the user that is used to create the container.
    Important
    The user must have permissions to write files to the host's file system.
  18. Enter the authentication credentials for accessing the remote host.
    • If you are using a private key to authenticate:
      1. Check the Private Key File box.
      2. Enter the full path to the private key file.
        Note
        This is the private key for the machine from which the user is accessing the management console.
    • If you are using a password to authenticate, enter the user's password in the Password field.
  19. Click Next.
    The second SSH Server Configuration page opens.
  20. If you want to use a directory other than the default provided, enter the full path to the deployment directory in the Path field.
    The default path is the user's home folder.
  21. If you want to retry the SSH login more than once, enter the number of retries in the Number of retries field.
  22. If you want to use a different retry delay than one second, enter the new retry delay in the Retry delay field.
  23. Click Finish.
    The wizard closes and the new container will appear in the list of containers. Initially the Active indicator may be red, but should turn green shortly after adding it. The Provisioned indicator may also show gray bars, but should turn green when the specified profiles are fully provisioned.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.