fix: return proper docker socket for remote Docker hosts #1281
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.
What does this PR do?
This PRs returns the default Docker host in the case the
tc.host
property is foundWhy is it important?
In #1161, we improved the resolution of the Docker socket depending on multiple scenarios (docker rootless, using a remote host, etc) but in the case the
tc.host
property is found, it simply returned it as the Docker socket path, which is incorrect. Instead, we must return the default docker socket path (/var/run/docker.sock
)Related issues