-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Failure on systems without SSH #152
Comments
I'm not really sure. The dependency actually just at runtime one, I've raised this issue to Open MPI folks, I don't remember the status. The thing is, Open MPI does not strictly need ssh if running in a single compute node or workstation or laptop. Open MPI is eagerly looking for For example, in my CI tests, if running under a small Docker image without ssh by default, I just do the following: export OMPI_MCA_plm_ssh_agent=false Here, In my own particular and biased opinion, I hate dependencies that are not strictly needed, and I'm generally not in favor of forcibly adding such dependencies as default ones. I'm totally fine with deps marked as optional or recommended, or mechanisms such Additionally, I'm a bit afraid of the consequences for users inadvertently installing the conda-forge openssh package in their conda environment, and from there any All that being said, if the rest of the Open MPI conda-forge user community feels that in this particular case it makes sense to add |
@dalcinl thanks for your quick answer. I agree that adding I'll take your workaround for my CI problems and as well for the execution of the packaged program I'm working. I was thinking adding |
That would be definitive solution, indeed. However, look here open-mpi/ompi#12386, although I'm a bit confused about this comment: open-mpi/ompi#12386 (comment). After reading all of that issue, at this point I'm not really sure what's the actual intended behavior. Maybe you should ask for a clarification: Is the absence of |
We encountered the same error in conda-forge/ambertools-feedstock#133 when testing the conda package with OpenMPI. Is it recommended to set this environment variable during the test? The conda-forge documentation (https://conda-forge.org/docs/maintainer/knowledge_base/#message-passing-interface-mpi) may need to add this information. |
@njzjz Whether to set the variable or not depends on whether you have the PS: Regarding conda-forge documentation, I personally have no involvement with any of that. I guess you can raise an issue or submit a pull request with whatever clarification you consider appropriate. |
Feel free to open an issue in https://github.com/conda-forge/conda-forge.github.io. |
the openmpi package now sets appropriate environment variables when run under $CONDA_BUILD, so it works without ssh and recipes should not need to set any I don't think we should do anything at runtime that's not openmpi's default behavior, so I'm not sure there's anything for us to do here. I also wish openmpi's default behavior were different, but I'm sure they have their reasons. It may be worth documenting that openmpi requires ssh by default and we don't depend on it since this should usually come from the system. The debian openmpi-bin depends on ssh-client, for example. |
Comment:
I tried to run an mpi application on a basic Rocky Linux 9 container with the conda-forge
openmpi
package. The application failed with the error message below. This error seems to be because the ssh client was not found.openmpi
depend onopenssh
? The Ubuntu and Rocky Linux packages do.Error message
The text was updated successfully, but these errors were encountered: