terraform get creates absolute target symlinks to disk based modules
Terraform Version
0.9.6
Desired Behavior
terraform get should create relatives target symlinks in the .terraform file (where possible) - this will make the terraform directory with embedded .terraform cache portable.
Steps to Reproduce
terraform get
silvermy
All 9 comments
without this it is painful for using terraform inside vagrant/docker. If i mount/share my project the symlinks are absolute to my host machine and mean nothing inside my test environment.
bcg62
on 2 Aug 2017
9639
bcg62
on 2 Aug 2017
This is also an issue with virtualbox shared folders for docker machine
nick4fake
on 4 Dec 2017
I'm facing this issue with the terraform docker image, when mounting volumes inside the Docker container the symlinked modules are not found.
mauricios
on 17 Mar 2018
In the next major version we plan to not create these symlinks at all and instead refer directly to the module's path relative to its caller. This is changing as part of a general effort to make the module paths more intelligible so that it's easier to understand what's going on when they appear in error messages, but I'm glad to hear that this change will be helpful for other reasons too.
apparentlymart
on 24 Mar 2018
@nick4fake for virtualbox and shared folders on windows this could be workarounded by fixing vbox param, see https://serverfault.com/questions/345341/cant-create-symlinks-in-virtualbox-shared-folders/367839#367839
and then starting Virtualbox as Administrator
mortalius
on 10 Jul 2018
:+1: for a fix for this (relative paths)
shaiguitar
on 22 Oct 2018
The change I mentioned above is merged into the master branch now and was included in the v0.12-alpha1 release. It will also be included in the forthcoming final release. Thanks all!
apparentlymart
on 22 Oct 2018
I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
![hashibot[bot] picture](https://avatars2.githubusercontent.com/in/8332?v=4&s=40)
hashibot[bot]
on 1 Apr 2020
Related issues
ketzacoatl
·
3Comments
larstobi
·
3Comments
ronnix
·
3Comments
darron
·
3Comments
rjinski
·
3Comments
Most helpful comment
In the next major version we plan to not create these symlinks at all and instead refer directly to the module's path relative to its caller. This is changing as part of a general effort to make the module paths more intelligible so that it's easier to understand what's going on when they appear in error messages, but I'm glad to hear that this change will be helpful for other reasons too.