Can I Start a Container in Privileged Mode When Running the systemctl Command in a Container in a CCI Cluster?
Currently, CCI does not support the privileged mode.
The privileged mode is enabled only when a container is allowed to access all devices on the host. CCI adopts the Kata hypervisor to isolate containers. Therefore, resources on the host are completely isolated from containers.
In other scenarios, you are advised to use the securityContext of Kubernetes to implement fine-grained permissions control, thereby ensuring the security and reliability of the container running environment.
Container Workload FAQs FAQs
- Why Service Performance Does Not Meet the Expectation?
- How Do I Set the Quantity of Instances (Pods)?
- How Do I Check My Resource Quotas?
- How Do I Set Probes for a Workload?
- How Do I Configure an Auto Scaling Policy?
- What Do I Do If the Workload Created from the sample Image Fails to Run?
- How Do I View Pods After I Call the API to Delete a Deployment?
- Can I Start a Container in Privileged Mode When Running the systemctl Command in a Container in a CCI Cluster?
- Why Does the Intel oneAPI Toolkit Fail to Run VASP Tasks Occasionally?
- Why Are Pods Evicted?
- Why Is the Workload Web-Terminal Not Displayed on the Console?
- Why Are Fees Continuously Deducted After I Delete a Workload?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore