首次创建ROS Docker容器遇setup.bash不存在错误，求排查方案

Hey there, let's break down this issue and fix it step by step!

The error bash: /home/ros/catkin_ws/devel/setup.bash: No such file or directory happens because you're trying to source a file that doesn't exist yet. Here's the root cause:

• Your Dockerfile creates the catkin_ws directory, but it never initializes or builds the Catkin workspace. The devel/setup.bash file is only generated after running catkin_make (or catkin build) on a properly initialized workspace.
• You added the source command to .bashrc, so every time you start the container, it tries to load that non-existent file, throwing the error.

Modify your Dockerfile to initialize and build the Catkin workspace after creating the directory. Here's the updated section:

# create catkin_ws
RUN mkdir /home/$USERNAME/catkin_ws
WORKDIR /home/$USERNAME/catkin_ws
# Initialize Catkin workspace and build it
RUN mkdir src && cd src && catkin_init_workspace
RUN catkin_make
# add catkin env
RUN echo 'source /opt/ros/kinetic/setup.bash' >> /home/$USERNAME/.bashrc
RUN echo "source $HOME/catkin_ws/devel/setup.bash" >> $HOME/.bashrc

关键改动说明： #

1. mkdir src && cd src && catkin_init_workspace: Creates the required src directory and initializes the Catkin workspace (this sets up the necessary CMake files to build your workspace).
2. catkin_make: Builds the workspace, which generates the devel directory and the setup.bash file inside it.
3. Used $HOME instead of hardcoding /home/$USERNAME for the .bashrc entry—this makes the command more flexible and avoids typos.

After updating the Dockerfile, rebuild your rosdocker image using VSCode's Docker plugin, then run the container again. The error should disappear.

If you run into similar issues in the future, use these steps to diagnose:

• Enter the container without loading .bashrc:
  Run this command to bypass the .bashrc auto-sourcing, so you can inspect the filesystem without the error blocking you:

  docker run -ti --name turtlebot3 --entrypoint /bin/bash rosdocker
  

  Once inside, check if the devel directory exists with:

  ls /home/ros/catkin_ws/
  

• Verify .bashrc contents:
  Manually check what's in your .bashrc to confirm the source commands are correct:

  cat /home/ros/.bashrc
  

• Check Docker build logs:
  When building the image in VSCode, look through the build output to see if catkin_make (or any other step) failed. If there was a permission error, you might need to adjust user permissions, but in this case, since you're working in the ros user's home directory, permissions should be fine.

内容的提问来源于stack exchange，提问作者pitosalas