如何将``--cap-add = XXX''等docker参数传递给在BlueData中运行的docker实例? [英] How do I pass docker parameters such as `--cap-add=XXX` to my docker instances running in BlueData?

问题描述

我想用--cap-add=IPC_LOCK运行一个容器.

根据BlueData 3.7 发行说明，支持IPC_LOCK:

According to the BlueData 3.7 release notes, IPC_LOCK is supported:

HAATHI-13547 :Docker配置现在包括所有已部署容器的默认IPC_LOCK功能. IPC_LOCK是某些客户应用程序所需的功能，也称为内存锁".实例化容器时，在Docker调用命令行上表示的Docker容器的允许功能现在明确包含此值.

HAATHI-13547: Docker configuration now includes default IPC_LOCK capability for all deployed containers. IPC_LOCK is the feature otherwise known as memlock, required by certain customer applications. The permitted capabilities of Docker containers as expressed on the docker invocation command line when instantiating a container now includes this value explicitly.

如何将诸如--cap-add=XXX之类的docker参数传递给在BlueData中运行的docker实例?

How do I pass docker parameters such as --cap-add=XXX to my docker instances running in BlueData?

推荐答案

您需要修改/opt/bluedata/common-install/bd_mgmt/releases/1/sys.config.查找已经具有允许功能列表的allowed_docker_caps.该元组上方的注释框列出了所有允许的功能.您可以从中选择.您必须在所有主机上更改文件，并在更新文件后重新启动每个bd_mgmt.

You need to modify /opt/bluedata/common-install/bd_mgmt/releases/1/sys.config. Look for allowed_docker_caps which already has a list of allowed capabilities. A block of comments above that tuple list all the capabilities allowed. You can choose from them. You have to change the file on all hosts and restart each bd_mgmt after updating the file.

请注意，更改后创建的所有新群集都将继承这些设置.

Note that all new clusters created after the change will inherit these settings.

这篇关于如何将``--cap-add = XXX''等docker参数传递给在BlueData中运行的docker实例?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！