graylog2 | installation script will perform an automated install

Is this is the query you're looking for?

1. (not related) You don't need to json_decode the result get_graylog_inputs.content. If the server on the over side sends the correct Content-type: application/json header, you should have a get_graylog_inputs.json entry containing the already decoded json result.
2. You don't need to loop twice. Remove the set_fact loop (which is not correct anyway) in your first file and use the value from your register directly in the second loop.
3. You did not show any example of your input data so I have to guess a bit here from your jmespath expression... but you basically don't need json_query at all and can stick to generic core ansible filters.

Here is how I see the solution in the second file once you cleaned-up the first:

There are few things to look at here starting from the concept of the hostPath volume:

A hostPath volume mounts a file or directory from the host node's filesystem into your Pod.

Pods with identical configuration (such as created from a PodTemplate) may behave differently on different nodes due to different files on the nodes

The files or directories created on the underlying hosts are only writable by root. You either need to run your process as root in a privileged Container or modify the file permissions on the host to be able to write to a hostPath volume

The hostPath would be good if for example you would like to use it for log collector running in a DaemonSet but in your described use case it might not be ideal because you don't directly control which node your pods will run on, so you're not guaranteed that the pod will actually be scheduled on the node that has the data volume.

But if that not the case, you also need to notice that type: DirectoryOrCreate is not best here as I see that you want to load a file. It would be better to use either:

• File: A file must exist at the given path

or

• FileOrCreate: If nothing exists at the given path, an empty file will be created there as needed with permission set to 0644, having the same group and ownership with Kubelet.

Lastly, there might be a permissions problem. As already stated:

The files or directories created on the underlying hosts are only writable by root.

Graylog is running with the userid 1100 which might cause a permission denial. Also, I have found a similar issue that might be helpful for you.

Docker is able to send logs from its standart output into graylog using gelf logger:

https://docs.docker.com/config/containers/logging/gelf/

When you dockerize your app, your app's localhost is not localhost of host machine. Simply remove all your fancy gelf-logger-libs from your python-code and put logs to stdout. Then docker will catch your logs and will send it to the graylog host.

Finally solved. According to documentation

GELF TCP does not support compression due to the use of the null byte (\0) as frame delimiter.

So after disabling compress on the log4j2 configuration we saw our log on the gray log server. The below code snippet is a working example

This seems to be a problem with the virtual box filesystem. I created an issue to composer and hopefully more insight will be gained.

https://github.com/composer/package-versions-deprecated/issues/21

I copied your composer.json to my local environment and ran composer update and had the same results. The problem is, that the class Sensio\Bundle\DistributionBundle\Composer\ScriptHandler does not exist with your config. So I executed composer require sensio/distribution-bundle, but then I got a version conflict:

I used this and It works for me.

From documentation composer suggests :

Lists all packages suggested by currently installed set of packages. You can optionally pass one or multiple package names in the format of vendor/package to limit output to suggestions made by those packages only.