What happens is vagrant compares fresh to cached and Pathname.new leaves a little bit at the start (#Pathname: ) which makes the comparison fail. I think one way to fix it would be to wrap File.expand_path around Pathname.new, but not 100% sure.
Steps to replicate...
Create a vagrantfile that uses docker with ansible installed locally.
Create and start the container with vagrant up.
Stop the container with vagrant halt.
Start the container up again with vagrant up and the message appears...
==> test: Vagrant has noticed that the synced folder definitions have changed.==> test: With Docker, these synced folder changes won't take effect until you==> test: destroy the container and recreate it.
When using docker, vagrant complains about sync folders changing when starting a container that has already been provisioned, I believe it stems from this line: https://github.com/jaugustin/vagrant-ansible-local/blob/641c3ba82aafc5ff162f08ae4049c687ca6bbc68/lib/vagrant-ansible-local/provisioner.rb#L6
What happens is vagrant compares fresh to cached and Pathname.new leaves a little bit at the start (#Pathname: ) which makes the comparison fail. I think one way to fix it would be to wrap File.expand_path around Pathname.new, but not 100% sure.
Steps to replicate...
==> test: Vagrant has noticed that the synced folder definitions have changed.==> test: With Docker, these synced folder changes won't take effect until you==> test: destroy the container and recreate it.