Custom Containers Deployment

Objective

This guide explains how to use Custom Containers Deployment on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

Ruk-Com Cloud PaaS allows creating software solutions packaged in Docker containers and storing them in Docker Hub or other registry (including private). This way you getAll benefits within the platform(e.g. scaling horizontal/vertical, logging, statistics, monitoring and alerting, configuration and file management, etc.) However, custom containers cannot be guaranteed to be compatible with applications within the container.

Tips:Ruk-Com Cloud provides a highly popular software stack and ready-to-use templates. Versions can be updated regularly. (certified container)

The guide provides basic instructions for defining Docker containers - how to create and manage all types of applications and services available in them.Docker HuborregistryYour personal custom

Customizing containers from Docker Hub

1. Open environmenttopology wizardBy clicking the buttonNew Environmentin the upper left corner of the dashboard.

In the left sidebar of the Docker wizard, you will see several blocks with different layer names. Each block can create a custom container based on the Docker image selected in these areas to divide and structure the topology according to your application.

You can select the desired layers and proceed by clicking Select Image to add the Docker images yourself.

2. When you open Select Container, there are several tabs to choose from.

• Quick Start - Popular software/recommended templates for the current layer (This tab may not be available. This depends on the settings from the hosting provider)
• Search - Helps you find the template you want from the central Docker Hub.
• Custom - can add your own templates from your personal registry or custom registry.
• Favorite - can store images expected to be used in the future for quick access.

As in the example above, for example, search for Docker Hub registry in the search bar. Type the desired full/partial name in the input field, such as dockersample/static-site and press Enter. A list of all dockersamples will be displayed, then click dockersample/static-site to add it to the server application layer. (They are checked and highlighted.) You can also select the required tags from the drop-down above.

You can select only a single Docker image or multiple instances in the same template (per layer). This way you can add additional images in different layers using the remaining blocks as needed.

3. Once you are back in the wizard with all your custom containers. You can start configuring and managing it like a normal node:

4. That's it, the environment based on your customized container will be created within minutes and will be displayed on the dashboard once created.

You can clickopen browserto open in the browser each container with the corresponding button next to it or all environments displayed through a given domain (Below the environment name) In the latter case, the application server or layer balancer template will open.

Note:Some custom containers may not have web pages. So you may receive a message.502 application downWhen the node was accessed through a browser, however, the image was not damaged. But what if you want to make sure the service works? You can check which processes are running inside the container by connecting to SSH. In cases where the application is deployed to a container that does not have a public IP on port 80/backend, you will see a 502 error - the service stopped specifically while trying to launch it. In this case, make sure that your container has a running HTTP service for handling incoming requests through the ports mentioned above.

Example of Docker application when clicking open browser

If you want to further configure your container You can add them directly through the dashboard. File Manager or Terminal after accessing via SSH as well as Web SSD. In both cases you will be given full root access to perform any modifications you want.

container from Custom/Private Registry

In addition to public templates available in the Docker Hub registry, Ruk-Com Cloud allows you to deploy private images from a custom registry. The platform recognizes and stores them separately), allowing you to use them in the same way as a public image. In the case of protected storage, you must provide appropriate references for access. This is done automatically (only once during the add). At the same time, all subsequent authentication for resizing the container or installing it is automatically performed.

Adding such images can be done through the Docker topology wizard.

1. Start by pressing the New Environment button, then click select image and select the tab.Custom

2. ClickAdd New Imageto enter the name of the registry where it is stored in the field. As a result, images from Docker Hub can be specified without setting the host registry at the beginning of the image name.

Tips:You do not need to specify specific tags during image addition, as you will be able to select the required tags during creation/modification. In addition, available images are automatically updated based on the images you choose to install. Therefore, there is no need to add the Docker template again because your application's code has been updated.

3. As for private storage You will need to add appropriate information to identify yourself throughUsernameandPasswordThen clickAddto continue

If you no longer want to use the template, you can click on the trash can icon (bin) in the upper right corner to delete it. Similarly, if you want to include images in a list, click the star icon (star) for later use.

4. In case you want to update access credentials via custom container. To do so, hover over the appropriate layer in the dashboard. Click the gear icon to expand the list. Then click on the Repo Credentials option.

5. When you click Repo Credentials, the container will contain credentials which you can edit by changing the name.LoginandPasswordfor your image

All it takes is adding a custom container from your repository. It is not the default Ruk-Com Cloud PaaS.

Tips:In case of any issues while running a custom Docker image on the platform. You can get help from technical experts at Stackoverflow