Open kinghuang opened 6 years ago
@kinghuang it's true that you can't add additional daemon config post deployment, but you can do this prior to deploying your cluster. If you look at the latest template, there's already a piece of the userData that does this. Add your custom parameters there and you'll be all set.
@FrenchBen Yes, I'm aware of modifying the UserData sections to add configs, which is what I'm doing right now. But, my point is it would be better if there were template parameters to add configs, with support in the UserData script to insert the additional configs, if specified.
That's why I mentioned adding a leading ,
, and the example result shows the actual output based on the current UserData script.
The Docker for AWS CloudFormation template generates
daemon.json
files for both managers and workers. But, there is no way to add additional daemon configurations without modifying the template.Expected behavior
There should be a template parameter to insert additional content into the
daemon.json
file for managers and workers. For example, there could beManagerDaemonConfigs
andWorkerDaemonConfigs
parameters that take literal JSON object members. The CF template can then add it to the generateddaemon.json
file, adding a leading,
as appropriate.CloudFormation Parameter:
Resulting config:
Note: This does not check for conflicts between the pre-defined configs and additional configs.
Actual behavior
There is no way insert additional content into
daemon.json
.Information
Relates to #101, #40, and #23.