Revision history [back]

Hey, @Doug! Thanks for your question. If you are using the pre-built version of the Docker container (autoware/autoware:latest-melodic or autoware/autoware:latest-melodic-cuda), then I recommend doing the following:

1. Create a new workspace in the shared_dir folder on your machine (cd $HOME/shared_dir && mkdir my_workspace).
2. Create a src folder in the workspace.
3. Run the Docker container.

In the Docker container, you should now see the ~/shared_dir/my_workspace/src folder. Inside this folder, run colcon create pkg <package_name> to create your new package. Once you've modified the package to your liking and added your code, go up to the root of the workspace (cd ~/shared_dir/my_workspace) and run colcon build. This should build your new package. To access the package, you'll need to "source" the workspace by running source /home/autoware/shared_dir/my_workspace/install/setup.bash --extend and you should then have access to your package through the normal ROS tools (roscd, rosrun, etc.).

Just a note: anything you do in the Docker container will be wiped out except data you store in the shared_dir folder, which will be available on your local machine in /home/<your_username>/shared_dir after you shut down the container.

Hey, @Doug! Thanks for your question. If you are using the pre-built version of the Docker container (autoware/autoware:latest-melodic or autoware/autoware:latest-melodic-cuda), then I recommend doing the following:

1. Create a new workspace in the shared_dir folder on your machine (cd $HOME/shared_dir && mkdir my_workspace).
2. Create a src folder in the workspace.
3. Run the Docker container.

In the Docker container, you should now see the ~/shared_dir/my_workspace/src folder. Inside this folder, run colcon create pkg <package_name> to create your new package. Once you've modified the package to your liking and added your code, go up to the root of the workspace (cd ~/shared_dir/my_workspace) and run colcon build. This should build your new package. To access the package, you'll need to "source" the workspace by running source /home/autoware/shared_dir/my_workspace/install/setup.bash --extend and you should then have access to your package through the normal ROS tools (roscd, rosrun, etc.).

Just a note: anything you do in the Docker container will be wiped out except data you store in the shared_dir folder, which will be available on your local machine in /home/<your_username>/shared_dir after you shut down the container.

Hey, @Doug! Thanks for your question. If you are using the pre-built version of the Docker container (autoware/autoware:latest-melodic or autoware/autoware:latest-melodic-cuda), then I recommend doing the following:

1. Create a new workspace in the shared_dir folder on your machine (cd $HOME/shared_dir && mkdir my_workspace).
2. Create a src folder in the workspace.
3. Run the Docker container.container using the run.sh script in the docker repository.

In the Docker container, you should now see the ~/shared_dir/my_workspace/src folder. Inside this folder, run colcon create pkg <package_name> to create your new package. Once you've modified the package to your liking and added your code, go up to the root of the workspace (cd ~/shared_dir/my_workspace) and run colcon build. This should build your new package. To access the package, you'll need to "source" the workspace by running source /home/autoware/shared_dir/my_workspace/install/setup.bash --extend and you should then have access to your package through the normal ROS tools (roscd, rosrun, etc.).

Just a note: anything you do in the Docker container will be wiped out except data you store in the shared_dir folder, which will be available on your local machine in /home/<your_username>/shared_dir after you shut down the container.