We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
I would expect ssh-ng://host:port as in ssh-ng://127.0.0.1:5000 to communicate over ssh via port 5000. Instead it treats it as part of the hostname.
ssh-ng://host:port
ssh-ng://127.0.0.1:5000
nix store ping --store ssh-ng://127.0.0.1:5000 "ssh: Could not resolve hostname 127.0.0.1:5000: Name or serice not known"
nix store ping --store ssh-ng://127.0.0.1:5000
Steps To Reproduce
nix store ping --store ssh-ng://host:port
Expected behavior
This should succeed if the ssh daemon is running on the expected port.
nix-env (Nix) 2.11.0
Additional context
A workaround is to set NIX_SSHOPTS to "-p port" in the environment but this doesn't work well for global configuration like substituters.
NIX_SSHOPTS
The text was updated successfully, but these errors were encountered:
Related to #3425
Sorry, something went wrong.
No branches or pull requests
Describe the bug
I would expect
ssh-ng://host:port
as inssh-ng://127.0.0.1:5000
to communicate over ssh via port 5000. Instead it treats it as part of the hostname.nix store ping --store ssh-ng://127.0.0.1:5000
"ssh: Could not resolve hostname 127.0.0.1:5000: Name or serice not known"
Steps To Reproduce
nix store ping --store ssh-ng://host:port
Expected behavior
This should succeed if the ssh daemon is running on the expected port.
nix-env (Nix) 2.11.0
Additional context
A workaround is to set
NIX_SSHOPTS
to "-p port" in the environment but this doesn't work well for global configuration like substituters.The text was updated successfully, but these errors were encountered: