The service name is a unique identifier of a service in the current cluster. Services use the service name+access port combination to access one another.
Yes. To do this, you can log in to your CVM and run the
docker login command to log in to the third-party image repository and pull the image.
Ensure that the CVMs in the cluster have public network bandwidth. Otherwise, public network services cannot be created.
For more information, see Setting Limit on Service Resources.
Applications in the container will have true root permissions when this option is enabled. We recommend that you enable this option when you need to perform higher-level system operations on applications in the container, for example, building an NFS server.
Check that there are sufficient CPU and memory resources. The container cannot be created if there are insufficient resources.
Yes. You can set the number of containers to 0 to release the resources and retain the service configurations.
Yes. Both rolling update and quick update are supported.
Yes. All containers and public CLBs for a service are terminated upon service deletion. Therefore, always back up the data in advance.
Containers use UTC by default. To solve the problem of an 8-hour difference between the container system time and the time you use the container, you can create a time zone file in Dockerfile.
RUN echo "Asia/shanghai" > /etc/timezone;
If you have not set a startup command or the default startup command is
bash, the container will exit once the startup procedure is completed. The process with PID 1 must be a resident process in the container to keep the container running. Otherwise, the container exits when this procedure ends. For some images such as centos, you can create services by running the
/bin/bash command with the
-c sleep 800000 parameter. Here,
sleep 800000 must be placed in different rows when you specify the parameters in the console.
Currently, certain images cannot start when the default parameters are used. These include clearlinux, ros, mageia, amazonlinux, ubuntu, clojure, crux, gcc, photon, java, debian, oraclelinux, mono, bash, buildpack-deps, golang, sourcemage, swift, openjdk, centos, busybox, docker, alpine, ibmjava, php, and python.