Creating a remote root container installs a new Fuse container on a remote host using SSH. Fuse 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.
![[Warning]](imagesdb/warning.gif) | Warning |
|---|---|
You cannot install remote root containers on Windows machines using Fuse Management Console. |
To create a remote root container:
Select from the top menu.
The Fuse Container Instances page opens.
Click .
The Create Fuse Container wizard opens.
In the Name field, enter a name for the new container.
If you want to make the new container a registry server check Make container a distributed registry server.
![[Tip]](imagesdb/tip.gif)
Tip It is recommended that if you create a registry server that you do not deploy any other services into the container.
If you want to be able to remotely debug the container check Enable remote debugging.
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.
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.
Click .
The Select profiles to install on the container page opens.
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 Fuse Profiles page.
Select one or more profiles to deploy to the container.
Click .
The Select the type of container page opens.
Select Remote root container.
Click .
The SSH Server Configuration page opens.
In the Hostname field, enter the name, or URI, for the host onto which the container will be deployed.
If your SSH configuration doesn't use the default port, enter the proper port in the Port field.
In the Username field, enter the name of the user that is used to create the container.
![[Important]](imagesdb/important.gif)
Important The user must have permissions to write files to the host's file system.
In the Password field, enter the user's password.
Click .
The second SSH Server Configuration page opens.
If you do not 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.
If you want to retry the SSH login more, or less, than six times, enter the number of retries in the Number of retries field.
If you want to use a different retry delay than one second, enter the new retry delay in the Retry delay field.
Click .
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.
 |  |  |
 |
