Lex Neva

I think this is due to incorrect caching in vault agent. My problem seems to match this comment: https://github.com/hashicorp/vault/issues/8953#issuecomment-656733690 Is consul-template known not to work properly when sent through vault...

As a note, this problem does not occur if you run `docker service create` manually.

@hamishforbes I'm seeing exactly the same problem you are with consul-template. Currently trying to figure out a solution. Did you solve this?

Thanks! Yes, as it turns out in our use case, we actually didn't even need the copy behavior, so our solution is to set nocopy on both containers. > Thanks...