1. Access the Environment Tology wizard by means of selecting the New environment button at the top-left dashboard’s corner.
Switch to the Docker tab at the top of the wizard. Inside, you’ll find a number blocks with different layer names to the left, where each of them provides an ability to select a Docker image with the required software and create a container based on it. You can add containers to any of the sections or several of them in order to divide and structurize the topology according to your needs.
Thus switch to the required layer and proceed with the Select Container button.
2. In the opened Select Container
frame, you’ll see a few tabs:
As an example, let’s use the search via the official Hub Registry - navigate to the same-named tab, type the full or part of the required name to the input field (e.g. jelastic) and hit Enter. After being shown the list of results, simply click on the prefered template to add it to the chosen layer (it will be marked with a tick and become highlighted). The necessary tag can be selected within the drop-down list next to the image name at the upper part of the frame.
Tip: Hovering over a particular image will expand the plank with a few supplementary functions:
Here, clicking on the More details string will open a separate browser tab with the corresponding repository page at Hub Registry.
And the star sign in the top right corner can be used for marking an image as Favorite
, so it will be permanently stored within the same-named tab to become easily accessible (just in the same way, it can be unticked for being removed from this list).
You can choose a single template per each layer, thus, if you’d like to change the picked image - just click on another one and confirm the replacement. Also, you can instantly switch between layer sections at the left pane to add any other container and customize your environment topology.
Click the Next button after you’ve finished the composing.
3. Once you are back at the wizard with all the required Docker nodes added, you can start configuring and managing them:
For more information on Docker nodes Сonfigurations (available within the same-named section at the bottom of the wizard), read the Docker Container Configuration guide.
Besides, you are able to manage the required settings even before an image is deployed - all the required data is automatically fetched upon accessing the appropriate settings section.
As soon as configurations are done, type the desired name for your environment, e.g. my-docker-env, to receive the similar one (we’ve added two more containers with Jelastic templates to other layer sections):
- any Docker environment layer can be scaled horizontally with the Multi Nodes feature; moreover, you can configure this for being performed automatically based on incoming load or define to get the appropriate load alerts via email
- if adding an image to the Application Server and/or Balancing layer, the whole environment will be automatically complemented with its own entry point (i.e. domain name) for being accessible over Shared LB
- enabling the Public IP option for the frontend container (i.e. which is intended to serve the requests, sent to the common environment domain) allows using custom domain names for your Dockerized apps and swap them
Now click on the Create button at the bottom of the wizard to initiate the environment creation.
4. That’s all! In a few minutes your environment with Docker containers will be created and will appear at the dashboard.
You can Open each container in browser with the corresponding button next to it or similarly access the whole environment via the assigned domain (shown below the environment name) - in this case, the application server layer’s template (or the balancer’s one if present) would be run.
- not all templates have the web-server running out of the box to provide the graphical user interface, thus you can get the 502 application down error while trying to access such a container through browser. However, that doesn’t mean this image is incorrect or corrupted - if you’d like to ensure the necessary service is really working, check the running processes inside a container using the SSH connection.
- in case an application, deployed to a container without the Public IP attached, is not listening to the :80th port on its backend, you’ll be shown the dedicated 502 - Service is down error page while trying to open it. This means you need to additionally adjust your container for ensuring it has a HTTP service run and set for handling the incoming requests through the abovementioned port.
In our case, the jelastic/tomcat8 node with Jelastic Hello World application packed will be launched if opening the environment.
If you’d like to make any additional configurations to a container, you can either perform this right through your dashboard (just click the Config button next to a node to open the embedded Configuration manager) or execute the required operations via terminal after accessing it via SSH. In both cases, you are granted the full root permissions for accomplishing the desired adjustments.