Configuring Bondy on Docker
In order to configure Bondy when using Docker you will have two options:
​Mounting a volume with the config files when executing the
docker runcommand​Creating your own docker image based on the official images
First, you will need to create your config files in a local directory e.g. ~/tmp/bondy/etc and map it to the bondy/etc directory exposed by the docker image.
Then, you will need to create a at least a minimal configuration for Bondy in that directory. The following are the snippets for a minimal configuration enabling anonymous clients to establish a session in a realm called com.myapp.test and also in the com.leapsight.bondy realm a.k.a. the administrative realm.
distributed_cookie = bondynodename = [email protected]aae.data_exchange_timeout = 1maae.enabled = onsecurity.allow_anonymous_user = onsecurity.automatically_create_realms = offsecurity.config_file = $(platform_etc_dir)/security_config.json
[{"uri" : "com.myapp.test","description" : "A test realm","authmethods" : ["wampcra", "ticket", "anonymous"],"security_enabled" : true,"users" : [],"sources" : [{"usernames" : "all","authmethod" : "password","cidr" : "0.0.0.0/0","meta" : {"description" : "Allows all users from any network authenticate using password credentials."}},{"usernames" : ["anonymous"],"authmethod" : "trust","cidr" : "0.0.0.0/0","meta" : {"description" : "Allows all users from any network authenticate as anonymous."}}],"grants" : [{"permissions" : ["wamp.register","wamp.unregister","wamp.subscribe","wamp.unsubscribe","wamp.call","wamp.cancel","wamp.publish"],"uri" : "*","roles" : ["anonymous"]}]},{"uri" : "com.leapsight.bondy","authmethods" : ["wampcra", "ticket", "anonymous"],"security_enabled" : true,"users" : [],"groups" : [{"name" : "administrators","groups" : [],"meta" : {"description": "The administrators of Bondy."}}],"sources" : [{"usernames" : "all","authmethod" : "password","cidr" : "0.0.0.0/0","meta" : {"description" : "Allows all users from any network authenticate using password credentials."}},{"usernames" : ["anonymous"],"authmethod" : "trust","cidr" : "0.0.0.0/0","meta" : {"description" : "Allows all users from any network authenticate as anonymous."}}],"grants" : [{"permissions" : ["wamp.register","wamp.unregister","wamp.subscribe","wamp.unsubscribe","wamp.call","wamp.cancel","wamp.publish"],"uri" : "*","roles" : "all"},{"permissions" : ["wamp.register","wamp.unregister","wamp.subscribe","wamp.unsubscribe","wamp.call","wamp.cancel","wamp.publish"],"uri" : "*","roles" : ["anonymous"]}]}]
Finally, you can run the docker image by mounting the local directory as the /bondy/etc volume adding the option -v ~/tmp/bondy/etc:/bondy/etc as shown in the following example:
docker run \-p 18080:18080 \-p 18081:18081 \-p 18082:18082 \-p 18086:18086 \--name bondy1 \-v ~/tmp/bondy/etc:/bondy/etc \-d leapsight/bondy:0.8.6
Another way to configure Bondy which might allow for further DevOps customisation is to create your own custom docker image from the official images.
The following example shows how to do it.
FROM leapsight/bondy:0.8.6 AS builder​COPY etc/security_config.json /bondy/etc/security_config.jsonCOPY etc/bondy.conf /bondy/etc/bondy.conf​
Lines 3 and 4 copy two configuration files from your custom image subdirectory/etc to the /bondy/etc/ directory.
You can find this example in the official docker repository.
The chances are that you will need to get some of the configuration values from OS environment variables.
Bondy Docker image allows you to define those variables using the unix shell convention syntax e.g.${VariableName}, as shown in the following snippet.
nodename = ${BONDY_NODENAME}distributed_cookie = ${BONDY_COOKIE}
Using the example above, the only modification required for Bondy Docker to substitute those variables with the OS environment counterparts is to add a .template extension to every configuration file containing variables.
FROM leapsight/bondy:0.8.6 AS builder​COPY etc/security_config.json /bondy/etc/security_config.json.templateCOPY etc/bondy.conf /bondy/etc/bondy.conf.template
Bondy Docker image will make the substitution automatically and place the resulting files in the same directory with the .template extension removed before calling the bondy executable.
Notice that variable substitution will fail if the environment does not have a value set for a variable found in the .template files. This will cause the Docker image to fail.
​
