After upgrading to rancher 1.6.17 rancher is using bind instead of volume mounts all of a sudden. The issue is explained in great detail in this github issue.
I would be really grateful if someone can confirm this behavior and whether or not this is fixable.
Scenario: We use Jenkins to deploy our software builds to rancher. Rancher-nfs then creates volumes where our application writes its logfiles for later analysis. However, our application is not running as root and thus is not allowed to write logs to the newly created rancher-nfs volumes. This causes the application to fail at start up.