title: Nifi failing to start due to missing snappyjava on int, but not on dev
body: <p>I have ansible scripts that install a docker container running nifi.  I've run these scripts on our dev box without issue.  However, when I run them on our int box I see the following error in the nifi-bootstrap.log, causing the whole nifi to die immediately at startup:</p>
  <pre><code>java.io.FileNotFoundException: /data/nifi/work/snappy-1.0.5-libsnappyjava.so (No such file or directory)
  </code></pre>
  <p>I checked the dev server where this is running and there is no /data/nifi/work directory and libsnappyjava doesn't exist anywhere on that server according to mlocate.</p>
  <p>The flow file is exactly the same between the two versions, I've done an md5sum to ensure that.  The only difference in the nifi.properties file is that the they each have their own VM's hostname injected into appropriate fields by ansible.  The nifi installation is part of a parent docker image that hasn't been touched and so should also be identical across images.</p>
  <p>I'm using a nifi tarball created by my company, containing some company specific jars etc, but it should be built on top of the latest nifi version.</p>
  <p>The only difference between the functional dev and non-functional int that I can tell is that I original installed a docker image running an older nifi version before upgrading the nifi to get the more recent nifi api.  I don't know if somehow running the old nifi before upgrading it would have made a change to our /data directory in some way preventing the upgraded nifi from failing?</p>
  <p>So why is my int looking for snappyJava when dev seems fine without it?</p>