Yeah, that's weird. Looks like you tried all of the things that I would have.
I'm not sure what user is used by the docker provisioner, but I assume it's root? (which you already tried). It would be nice to see the CLI command that the provisioner ultimately uses (which presumes it uses the CLI). `--debug` doesn't give you that, does it? One more thing: What happens if you copy your files to a native spot in the VM and use that as the host side of the docker bind mount as a troubleshooting step. I'm wondering if it's permissions problem in the container or a complete failure to mount the volume (e.g., if the provisioner is corrupting the args somehow). Your description was ambiguous--I'm not sure if the process can't read the files or if the files are just missing (can you list them from a `docker exec`?). On Fri, Dec 27, 2019 at 11:30 AM Alexander Solla <alex.so...@gmail.com> wrote: > > > On Thursday, December 26, 2019 at 4:51:08 PM UTC-8, Jamie Jackson wrote: >> >> Rewriting my first sentence: >> >> Does /tf exist in the Vagrant VM? If it doesn't, you'll need to add a >> (vagrant-managed) shared directory from the `tf` directory on your host to >> a `/tf` directory on your guest. >> > > Yes, /tf does exist on the vagrant vm, as an NFS share. (And the Docker > container can access it IF I run the docker run command "by hand" in the > container.) That's what's confusing me -- everything "should" be working, > but "somehow" permissions are set incorrectly when Vagrant's docker > provisioner does the docker run. > > Thank you for checking in. > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to vagrant-up+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/565ab372-4e43-4a5f-a7eb-dceff8916f4d%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/565ab372-4e43-4a5f-a7eb-dceff8916f4d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CA%2BonWPchn-97W2vX1EzsyiOFm_1xwZvcq-Hwc%3DONNP%3DzLK5MeQ%40mail.gmail.com.
