-
Notifications
You must be signed in to change notification settings - Fork 142
Open
Description
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 theops/Docker
directory. The second one isn't maintained anymore and should be removed, or?- Bonus Questions: The
ops/packer
,ops/terraform
andops/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).
- Bonus Questions: The
- 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" (c4123e4), 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.
- in production setups, database will get initialized once either manually from outside a container or by starting a container with
Thanks and keep up the great work!
Metadata
Metadata
Assignees
Labels
No labels