bug: added support for relative volume mounts in docker compose #1186
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.
Related Issue
Closes: #1049
Describe the changes you've made
Created three new functions in
pkg/clients/docker/docker_client.go
:CheckBindMounts
: Returns true if any relative paths are being used in volumes in compose fileReplaceRelativePaths
: Replaces relative paths with absolute path with respect to host filesystem which it obtains by callingGetHostWorkingDirectory
. Creates a new kdocker-compose.yml file with the changes.GetHostWorkingDirectory
: Inspects keploy-v2 docker container and gets the mount path for /files. This is the application directory in the host file system.Added an if block in
pkg/hooks/launcher.go
which runs for docker compose related commands and checks if relative file paths are present and replaces them.Type of change
Please let us know if any test cases are added
NA
Describe if there is any unusual behaviour of your code(Write
NA
if there isn't)NA
Checklist:
Screenshots (if any)
NA