Updated Dockerfile .bashrc creation to be more readable

[BruceMcRooster]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

This makes the actual script that is written to ~/.bashrc by the Dockerfile more readable.
Readability is usually a good thing. Just look at this.

RUN printf '\n# automatically generated by Dockerfile \n\
source "/opt/ros/humble/setup.bash" --                \n\
cd rb_ws                                              \n\
colcon build --symlink-install                        \n\
source install/local_setup.bash                       \n\
chmod -R +x src/buggy/scripts/                        \n\
source environments/docker_env.bash                   \n\
\n' >> ~/.bashrc

Beautiful 👌

Related Tickets & Documents

I referenced making a change like this when reviewing another PR; here was my comment. It was slightly modified to ensure consistency and that it worked

Testing

This has been tested in the Docker container, but if you want to try it yourself, boot up a container. You shouldn't see any errors in the Dockerfile or in bash when it starts up. Checking the bottom of ~/.bashrc should show the correct code, reproduced below, with no weird trailing characters, aside from some spaces that were added for better formatting of the Dockerfile.

# automatically generated by Dockerfile 
source "/opt/ros/humble/setup.bash" --                
cd rb_ws                                              
colcon build --symlink-install                        
source install/local_setup.bash                       
chmod -R +x src/buggy/scripts/                        
source environments/docker_env.bash                   

[BruceMcRooster]

I used printf because it supports \n everywhere, while echo typically requires the -e flag and I was having problems where it was including -e in the output.