linusdm
Hi,
I’m hitting an error when trying to use the :ssh module in a docker container:
[notice] Erlang SSH :client version: 5.0.1 (OpenSSL 3.0.9 30 May 2023).
Address: 1.2.3.4:56789
Peer server version: ~c"SSH-2.0-OpenSSH_for_Windows_8.1"
Peer address: 4.3.2.1:22
Disconnects with code = 11 [RFC4253 11.1]: Internal error
State = {key_exchange,client,init}
Module = ssh_connection_handler, Line = 1387.
Details:
Reason: {badmatch,{error,enoent}}
I’m passing in the {:silently_accept_hosts, true} option, but I’m probably still missing some setup to use the SSL client in the docker environment (locally, not in docker, it works fine).
# hostname, username, passwords are charlists
:ssh.connect(hostname, port, [{:user, username}, {:password, password}, {:silently_accept_hosts, true}])
The runner image in Dockerfile has the openssl installed (which is added by default when using mix release), but maybe there is still some package missing?
I’m not sure what needs to be available on the host Docker OS (debian in my case) to enable ssh client communication. Any help is greatly appreciated!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
D4no0
I had this issue when installing OTP-26 on my mac, turns out openssl 3 is not officially supported yet in OTP.
linusdm
The default
USERDIRfor the ssh application is/home/LOCALUSER/.ssh(e.g.~/.ssh). This folder doesn’t exist in the docker debian environment. Passing in the:user_diroption when connecting, pointing it to a writable folder, solves the issue:This is the folder where
authorised_keys,known_hosts, etc. are kept.I’ve created a dedicated folder in the Dockerfile, and passed it in as an environment variable, so it can be used when connecting (or omitted when not in docker).
linusdm
Although I’m happy I found the culprit, it baffles me that there is nothing in the original error hinting to a filesystem related issue… I guess this is deep in the erlang ssh-code…
LostKobrakai
{error,enoent}is a filesystem related error, but I agree it’s not much of a signal.