Pre-create badger directory in Docker image

[freef4ll]

Which problem is this PR solving?

#4906

Description of the changes

• Create directory for badger in a non-root environment so that existing setups do not break.

How was this change tested?

• Tested permissions in a minimal container.

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: yarn lint and yarn test

[yurishkuro]

I don't think this change is going to help. First, there is no requirement that the actual directory is /badger, it's up to user to specify what it is. Second, all this change is doing is creating a dir inside the container file system during image creation, whereas in real deployment such directory would need to be mapped to host file system.

[freef4ll]

Correct, but if it is mapped by a named volume then it works for the default configuration.

[yurishkuro]

Correct, but if it is mapped by a named volume then it works for the default configuration.

why would it work? if you have files on host file system owned by a different user-id, then the owner of in-container directory still not going to match the permissions on those files. Can you show commands that demonstrate a successful test?