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

Question on docker and use of ROS node of YDLidar x4 #1

Open
pebe-espana opened this issue Mar 7, 2023 · 0 comments
Open

Question on docker and use of ROS node of YDLidar x4 #1

pebe-espana opened this issue Mar 7, 2023 · 0 comments

Comments

@pebe-espana
Copy link

Hi,
I have a question not directly pertaining to your GitHub ROS-YDLidar-x4-docker code, but concerns the basic installation steps around YDLidar.
I am running my robot from within a docker ROS environment on a raspi4, no ROS installed on Raspi host.
Latest extension to it is now the YDlidar-X4.
Now the installation of the Lidar comes in two steps - setting up the SDK build process, which then allows second step of either the test_code or the ROS node to start the laser acquisitions.
System runs as desired after installation of the YDLidar SDK, if the test_code runs directly on host or in a ROS environment directly on host (tested on separate Ubuntu system).
But the installed SDK build on Raspi host is not accessible from within a docker container with ROS system, as ROS node needs access to some SDK package parts to be built itself.
As a "solution/work around" I have repeated the SDK install and build process within root during the startup of the container - effectively duplicating the build on host inside the container on it's root. Then it ROS node works, communicating back to rviz on another powerful PC etc etc.
Although working, it does not seem to me to be the proper way to use the docker container, as every startup of container now repeats installation steps...
Any clue where I am going wrong during install and docker container setup? Where does SDK build feature in your docker environment? Happy to communicate further details...
Regards, Peter

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

No branches or pull requests

1 participant