Hi,
We're using Nifi in a containerized environment (using docker-compose for
local development and test, and docker swarm in production).
The current docker image doesn't have a lot of environment options, meaning
if you want to run Nifi with some custom config like the one below :
environment:
- NIFI_WEB_HTTP_HOST=xxx
- NIFI_CLUSTER_HOST_NAME=xxx
- NIFI_CLUSTER_HOST_PORT=xxx
- NIFI_CLUSTER_PORT=xxx
- NIFI_ZOOKEEPER_CONNECT_STRING=xxx
- NIFI_CONTENT_REPOSITORY_ARCHIVE_MAX_USAGE_PERCENTAGE=xxx
- CONFIG_URI_LABEL=xxx
You need to create your own "wrapper" docker image (extending the base
apache nifi one).
Stuff that we typically to in a nifi installation is
- change values in nifi.properties (a generic solution could be created for
that where nifi property keys could be provided as environment variables to
the docker container)
- install custom processors (nar files)
- custom log configuration (logback.xml)
- custom bootstrap values
- copy flow templates in nifi so they can be used immediately after startup.
Have you ever thought of extending the current docker image, to allow a
little bit more customization like this ones above.
Some other things I noticed :
- the readme on https://hub.docker.com/r/apache/nifi/ doesn't mention docker
usage it all. seems to be the default nifi readme.
- The current docker image contains 2 layers of 1gb each. I'm guessing this
is the result of a) downloading and untarring the nifi distribution and b)
executing the chown command. Is there a reason these are spread out over 2
docker run commands ?
f5f88f68e088: Downloading [=>
] 25.9MB/978MB
5ed4b763cde4: Downloading [=>
] 34.02MB/978MB
--
View this message in context:
http://apache-nifi-users-list.2361937.n4.nabble.com/NiFi-Docker-tp2562.html
Sent from the Apache NiFi Users List mailing list archive at Nabble.com.
