Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use 'comand -v' to check presence of socat anywhere in path #869. #932

Conversation

jvortmann
Copy link

When using a base image that is not the provided ones (some custom container), the socat utility could have been installed on a diferent place than /usr/bin. For instance, yum on CentOS installs socat on /usr/local/bin.

This commit just rely ou 'command -v' to check if socat exists anywhere on the path.
Also, if socat is installed anywhere by /usr/bin before this, the access to services failed
silently.

@jvortmann jvortmann changed the title When using a base image that is not the provided ones (some custom container), the socat utility could have been installed on a diferent place than /usr/bin. For instance, yum on CentOS installs socat on /usr/local/bin. Use 'comand -v' to check presence of socar anywhere in path #869. Mar 22, 2015
@jvortmann jvortmann changed the title Use 'comand -v' to check presence of socar anywhere in path #869. Use 'comand -v' to check presence of socat anywhere in path #869. Mar 22, 2015
@bradrydzewski
Copy link

thanks!

bradrydzewski added a commit that referenced this pull request Mar 22, 2015
…in_path_using_command_v

Use 'comand -v' to check presence of socat anywhere in path #869.
@bradrydzewski bradrydzewski merged commit aa3eeda into harness:master Mar 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants