|CI status||No Continuous Integration|
|Tags||No category tags.|
Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)
A sandboxing plugin for launch_ros
Install the project as a python package:
$ python3 setup.py install --user
Check that your user is in the Docker user group:
If you dont see
docker, then add your user to the Docker group:
$ sudo usermod -aG docker $USER
A working example is provided in examples/minimal_sandboxed_node_container.launch.py.
Creating a sandboxed node is very similar to creating a regular launch file.
SandboxedNodeContainer() action like you would with a regular launch file, but make sure to provide the
Adding nodes is also similar to regular launch files, however, you should use
A launch file with nodes running as a certain user would look like:
def generate_launch_description() -> launch.LaunchDescription: ld = launch.LaunchDescription() ld.add_action( launch_ros_sandbox.actions.SandboxedNodeContainer( sandbox_name='my_sandbox', policy=UserPolicy(run_as=User.from_username('dashing')), node_descriptions=[ launch_ros_sandbox.descriptions.SandboxedNode( package='demo_nodes_cpp', node_executable='talker'), launch_ros_sandbox.descriptions.SandboxedNode( package='demo_nodes_cpp', node_executable='listener') ] ) )
This library is licensed under the Apache 2.0 License.
This stack supports the following ROS 2 releases:
|ROS 2 Release||Development||Source Debian Package||X86-64 Debian Package||ARM64 Debian Package||ARMHF Debian package|
Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.
Please read through this document before submitting any issues or pull requests to ensure we have all the necessary information to effectively respond to your bug report or contribution.
Reporting Bugs/Feature Requests
We welcome you to use the GitHub issue tracker to report bugs or suggest features.
When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
- A reproducible test case or series of steps
- The version of our code being used
- Any modifications you've made relevant to the bug
- Anything unusual about your environment or deployment
Contributing via Pull Requests
Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
- You are working against the latest source on the master branch.
- You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
- You open an issue to discuss any significant work - we would hate for your time to be wasted.
To send us a pull request, please:
- Fork the repository.
- Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
- Ensure local tests pass.
- Commit to your fork using clear commit messages.
- Send us a pull request, answering any default questions in the pull request interface.
- Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
GitHub provides additional document on forking a repository and creating a pull request.
Finding contributions to work on
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
Code of Conduct
This project has adopted the Amazon Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact firstname.lastname@example.org with any additional questions or comments.
Security issue notifications
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our vulnerability reporting page. Please do not create a public github issue.
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
We may ask you to sign a Contributor License Agreement (CLA) for larger changes.