ms-users | handling user 's management via amqp transport layer | Pub Sub library

Processor does not let you chaining new operator in downstream DSL, you should use a transformValues so use can continue to use Stream DSL:

1. First extract Headers from inside a ValueTransformerWithKey

i have a feeling that you are confusing something, since the title of your question mentions chef-solo when you are really using chef-zero (--local-mode).

you should definitely favor chef-zero over chef-solo (but i won't get into the reasons why).

in both cases (using chef-zero or chef-solo), you will have to download all the cookbooks and make verify chef-client knows where are the cookbooks located.

if you ase using chef-zero, here are some references:

Local mode does not require a configuration file, instead it will look for a directory named /cookbooks and will set chef_repo_path to be just above that. (Local mode will honor the settings in a configuration file, if desired.) If the client.rb file is not found and no configuration file is specified, local mode will search for a config.rb file.

client.rb settings:

chef_repo_path: The path to the chef-repo containing cookbooks and other files, such as environments or data bags, when running Chef Infra Client in local mode.

cookbook_path: The sub-directory for Chef Infra Client cookbooks. This value can be a string or an array of file system locations, processed in the specified order. The last cookbook is considered to override local modifications.

since i see that you are using berkshelf, you can use vendor sub-command to download all the cookbooks dependencies and place them in the same directory. then, have a custom configuration for chef-client, that sets the value of cookbook_path to the same directory which you used in conjunction with berks vendor, and finally execute chef-client.

I think you might be running other consumer instance of same group, for testing purpose you can change stream groupname

The problem was I was missing the execution permision for the binary RUN chmod +x /work/application.

Complete Dockerfile:

Instead of writing {{ permissions }}, you iterate over the queryset, and each time print the name of the permission, like: