@Juan, Thanks for the tip, probably not going to mount logs as using Elastic filebeat to tail any live docker container logs - assuming that nifi docker is configured to use the standard "docker log" API.
I've also found from experience that it is safer to move the default root Docker volume location from /var/lib to a larger drive as it can blow up and fill up root very quickly depending on how the internal docker app behaves or writes logs. On Thu, 25 Oct 2018 at 14:15, Juan Pablo Gardella < [email protected]> wrote: > I suggest to be careful when mount log directory. In one day fills some > Gigabytes. If you want to mount logs, adjust the logging. > > On Thu, 25 Oct 2018 at 10:07 Stephen Greszczyszyn <[email protected]> > wrote: > >> >> >> On Thu, 25 Oct 2018 at 12:50, Peter Wilcsinszky < >> [email protected]> wrote: >> >> But even with 1.8 I'll need to declare the host mount directory somehow >> via docker-compose, as how will the built docker image on dockerhub know >> where to locally mount the internal $(NIFI_HOME) volumes as described below? >> >> VOLUME ${NIFI_LOG_DIR} \ >>>> ${NIFI_HOME}/conf \ >>>> ${NIFI_HOME}/database_repository \ >>>> ${NIFI_HOME}/flowfile_repository \ >>>> ${NIFI_HOME}/content_repository \ >>>> ${NIFI_HOME}/provenance_repository \ >>>> ${NIFI_HOME}/state >>>> >>> >>> Yes you should specify volumes explicitly if you use 1.7.1, but also you >>> should specify an extra separate volume to use for your incoming SFTP data. >>> >>>
