Closed Sol-Han closed 2 years ago
We experienced the exact same problem when we tried to run the docker compose setup on our infrastructure. Can we discuss this problem in this issue, so it's publicly available to everyone?
Posting my answer here in case it helps others. The original issue is about missing cyclonedds.xml
in the bridge container.
If you don't see the cyclonedds.xml
file in the bridge container, it could be that docker compose is not run from inside the docker/compose
directory. There is a cyclonedds.xml file in that directory which gets mounted to the container by this line. It uses the .
current path. You can try changing this path to the absolute path of the docker/compose
directory containing the cyclonedds.xml
file.
We will ask this issue as email. Thank you.