The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
After some troubleshooting with @shlokgoel, we found that this was caused by multiple instances of the Autoware.ai Docker containers running in the background. When you launch a Docker container which creates a shared volume (like the shared_dir folder in Autoware.ai), it binds the folder on your host to a directory in the container. If you then launch another container which attempts to bind to the same folder on the host, it will fail silently. The shared_dir folder will still appear in your container but it won't be attached to the host folder.
Resolution: When you are done working in an Autoware.ai Docker container, make sure to type exit and hit enter in the terminal in which you launched the container. Closing that terminal will leave the container running in the background.
You can verify if any containers are running in the background by running docker container ls in a new terminal. If there are any "detached" containers (meaning you don't have terminal access to them anymore), you can stop them with docker container stop <container_name>.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
