Status of Container Images

I'd like to raise a few questions around the current container images of Iris:
- Currently there are two `Dockerfile`s, one in the root directory and one in the `ops/Docker` directory. The second one isn't maintained anymore and should be removed, or?
- Bonus Questions: The `ops/packer`, `ops/terraform` and `ops/charts` are also outdated and don't seem to be maintained. Should those go away, too? (I might be looking into proving an updated helm charts with version 2 in the next weeks).
- Is there any plan to provide pre-build container images? There seems to be an "official" registry (https://quay.io/repository/iris/iris), but the images are 3 years old. If there's no plan I will start building "unofficial" images.
- I'm currently trying to improve the container image by running the image "rootless" (https://github.com/linkedin/iris/commit/c4123e450cef36a4c5271e4f2550d55f5f73d434), which would mean that iris user has only limited write access to the container image. I'm having trouble finding a good solution for the sender rpc log file. any hints/comments here? I'm currently patching the config file to update, but this doesn't seem to be the best way to handle this.
- Was there a specific reason for the `initializedfile`? It doesn't seem to provide any real benefit to me in a container environment.
- in production setups, database will get initialized once either manually from outside a container or by starting a container with `DOCKER_DB_BOOTSTRAP`
- In development setups, containers will be rebuild quite often and reinitialize will happen anyway as the `initializedfile` isn't existing.

Thanks and keep up the great work!

Start by comparing the root Dockerfile with ops/Docker and reviewing the status of ops/packer, ops/terraform, and ops/charts. The issue also raises rootless logging, initializedfile, and prebuilt-image questions; first get maintainer decisions that turn these questions into a scoped change, with the selected files and acceptance criteria recorded.

Written by the indexing model from the issue text.