Allow defining the name of the docker-compose symlink #544
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I bumped into a problem with docker-compose where every docker-compose command failed with:
Found out it's related to docker-composes use of the environment variable
TMPDIR
, usually pointing to /tmp or /var/tmp, and that docker-compose expects to be able to run scripts from this path. Being able to run scripts from these locations is not a security best practice, so I made a wrapper script installed at/usr/local/bin/docker-compose
where I set TMPDIR to a safer location, before running the actual docker-compose binary. This wrapper script now conflicts with the default symlink file created by this fabulous module, so this PR adds the ability to give this symlink another name.The issues I'm referring to is also described in more detail on this stackoverflow post:
https://stackoverflow.com/questions/57796839/docker-compose-error-while-loading-shared-libraries-libz-so-1-failed-to-map-s