<p><strong>1. Why can&#39;t I repeat the service name? </strong></p> <p>The service name is the unique identifier of a service under the current cluster. Services can be mutually accessed through the service name + access port.&nbsp;</p> <p>&nbsp;</p> <p><strong>2. Can I use third-party images when creating a service?</strong></p> <p>You can log in the third-party image repository by logging in the host and executing the docker login command.</p> <p>The console using a third-party image will be available soon.</p> <p>&nbsp;</p> <p><strong>3. How can I enter information about memory and CPU limits? </strong></p> <p>Request and limit</p> <p>request: It does not limit the resources actually used by the container, and it is only used for resource scheduling when creating the container. Only when the node&#39;s available resource is greater than this value, the container can be scheduled successfully.</p> <p>limit: It limits the maximum available resources of the container and is not related to resource scheduling.</p> <p>CPU limit</p> <p>CPU limit is to limit the time slices that the container can use by setting the number of CPU cores. CPU resources use core as the unit, and decimals are acceptable.</p> <p>1. If you set both CPU limit and CPU request, both of them will take effect.</p> <p>2. If only CPU limit is set, it will automatically is equal to CPU limit.&nbsp;</p> <p>3. If only CPU request is set, it will take effect and place no upper limit on actual CPU use.</p> <p>4. limit needs to be greater than or equal to request.</p> <p>Memory limit</p> <p>Memory limit is to limit the maximum amount of memory that the container can use. Memory uses MB as the unit.</p> <p>&nbsp;</p> <p>1. Memory request only takes effect during container scheduling, which will determine whether the available memory resources are greater than the memory request, or else scheduling will fail.</p> <p>2. A container identified with memory limit can use the maximum memory. When memory used by the container exceeds the upper limit, it will be killed. Therefore, in order to ensure normal operation of the container, limit request = limit.</p> <p>&nbsp;</p> <p><strong>4. Does update service support rolling update?</strong></p> <p>No. It will be available soon.</p> <p>&nbsp;</p> <p><strong>5. How can I set the container system time as Beijing time? </strong></p> <p>The container uses UTC time by default. When using the container, there is often a difference of 8 hours between the system time and Beijing time. There are two solutions. One is to use environment variables even TZ = Asia / shanghai, and the other is to create a time zone file in dockerfile.</p> <p>RUN echo &quot;Asia/shanghai&quot; &gt; /etc/timezone;</p> <p>Environment variables need to be added each time when creating a service. Dockfile creates a time zone image to solve this problem once and for all.</p>