Skip to main content

Docker image support specification

This chapter will introduce you to Rainbond's support specification for creating components based on Docker images.

Image Support Specification​

Rainbond's way of creating components based on existing standards is the fastest and most compatible way.Here we will describe what images can run on Rainbond from the following aspects：

image that doesn't work​

Here we first explain which images cannot be run, which is very important.

  • basic system environment

The basic system images represented byalpine centos debian are necessary for us to make component images, but they cannot be directly run on Rainbond, why? Because they start the process is not running in the foreground by default, that is, the container will exit when it starts.Only open stdin for TTL interactive runs when running locally.

  • Basic language&tools

At present, many developers use Docker images to distribute command-line tools, such as golang compilation environment, docker compilation environment, maven compilation environment, and so on.They don't work for the same reasons as the first category.

runnable image​

In addition to the image types described above, the following types of components are recommended to be created based on：.

  • middleware class

For example,Mysql Mongo Redis Tomcat nginxand other frequently used middle price components.

  • web tools

For examplephpmyadminetc.

  • basic component class

For example,sFTPcomponent,minioobject storage components, etc.

  • Other various component images that provide TCP or UDP protocol components

Mirror Detection Specification​

  • The image can be obtained normally by the Rainbond cluster server

    • The provided image name is accurate and exists in the corresponding image repository

    • For private warehouse images, please provide the account password

    • For self-built warehouses, please configure HTTPs or configure Docker trust for Rainbond cluster nodes

  • Rainbond will get the following property information from the image：

    • Port, the Expose port information configured in the dockerfile will be obtained.
    • Environment variables, environment variables are the recommended custom configuration methods under cloud native, and are also recommended users of Docker image custom configuration.
    • Storage mount, the volume information configured in the dockerfile will be obtained

    The components created by Docker compose are only obtained from the compose configuration, and the components created by docker run are obtained from the create command and image.

  • Component memory allocation setting：

    The components created with the image use 512M memory allocation by default. If the components created by dockerrun or docker compose show that the memory parameters are set, the settings will prevail.

  • Component deployment type setting：

    Components created from images are set toby default for stateless deployment typeAfter version 5.1.3, the default setting isfor stateful deployment type when the image name is the following value:

    • mysql
    • mariadb
    • mongo
    • redis
    • tidb
    • zookeeper
    • kafka
    • mysqldb
    • mongodb
    • memcached
    • cockroachdb
    • cockroach
    • etcd
    • postgres
    • postgresql
    • elasticsearch
    • consul
    • percona
    • mysql-server
    • mysql-cluster

    For example the following image will be deployed as stateful type：

    • mysql:latest
    • hub.example.com/xxx/mysql:5.5
    • xxx/mysql:5.7