-
Notifications
You must be signed in to change notification settings - Fork 1
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
Host key verification failed when starting micro-RTPS #5
Comments
This isn't an issue with the tutorial itself, the problem lies in the see: https://github.com/eProsima/Micro-XRCE-DDS/blob/master/.gitmodules
The URLs within the I have raised this as separate PR on the eProsima repo itself. |
The current `.submodules` file is causing an issue when instantiating within a Docker environment. See FIWARE/tutorials.Fast-RTPS-Micro-RTPS#5 - this can be simply fixed by using HTTP urls rather than SSH
* Switch to use public HTTP endpoints The current `.submodules` file is causing an issue when instantiating within a Docker environment. See FIWARE/tutorials.Fast-RTPS-Micro-RTPS#5 - this can be simply fixed by using HTTP urls rather than SSH * Change colon to Slash
Hi Jason, sorry for the late reply. After moving forward, the problem now is that when executing the command
This happens because the submodules of that revision are not fetched.
I went this far, I'll continue tomorrow but wanted to list my findings.. |
This is my dockerfile so far:
|
Hi, there's an issue in the Dockerfile when creating the micro-RTPS image.
This happens when building the docker image
docker build -t fiware/micro-rtps-examples ./micro-rtps
At this line:
git clone --recursive https://github.com/eProsima/micro-RTPS.git
The error:
This happens when trying to clone using the ssh form on the dependencies.
Probably because the host verification is failing or there's an invalid key when trying to ssh github.
For verification purposes, running this command locally works fine:
git clone --recursive https://github.com/eProsima/micro-RTPS.git
The text was updated successfully, but these errors were encountered: