nifi.sensitive.props.key is cleared upon restart
Summary
After pulling registry1.dso.mil/ironbank/opensource/apache/nifi:1.15.2, running, then restarting, the nifi.sensitive.props.key value that was randomly generated during the run is cleared by the restart
Steps to reproduce
$ docker pull registry1.dso.mil/ironbank/opensource/apache/nifi:1.15.2
$ docker run --name nifi -p 8443:8443 -d registry1.dso.mil/ironbank/opensource/apache/nifi:1.15.2
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2f79d86fdb79 registry1.dso.mil/ironbank/opensource/apache/nifi:1.15.2 "../scripts/start.sh" 9 seconds ago Up 11 seconds (health: starting) 8000/tcp, 8080/tcp, 10000/tcp, 0.0.0.0:8443->8443/tcp nifi
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2f79d86fdb79 registry1.dso.mil/ironbank/opensource/apache/nifi:1.15.2 "../scripts/start.sh" About a minute ago Up About a minute (healthy) 8000/tcp, 8080/tcp, 10000/tcp, 0.0.0.0:8443->8443/tcp nifi
$ docker restart nifi
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2f79d86fdb79 registry1.dso.mil/ironbank/opensource/apache/nifi:1.15.2 "../scripts/start.sh" 2 minutes ago Exited (0) 12 seconds ago nifi
What is the current bug behavior?
as shown above, nifi container won't restart and stay up
this might be due to the nifi.sensitive.props.key value
after the initial successful run, docker cp of nifi.properties shows the randomly generated key
after the restart, docker cp of nifi.properties shows that the nifi.sensitive.props.key value is gone
What is the expected correct behavior?
nifi will restart fully and continue to run
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
Tasks
-
Bug has been identified and corrected within the container