robojackets/robocup-software-dev repository overview

⁠Basics

If you are using an Intel/AMD (x86_64) system, replace <architecture> with amd64

If you are using an ARM-based system, replace <architecture> with arm64

⁠Steps to Use

• docker pull robojackets/robocup-software-dev:<architecture>
• docker run -p 6080:6080 -p 5901:5901 -p 8081:8081 -d robojackets/robocup-software-dev:<architecture>
• Open http://localhost:6080/⁠
• It will ask for a password which is "password" by default
• The first time you open noVNC, the display might not be scaled properly. If so, use the buttons on the left side to fix the scale.
• Our repository will be at ~/robocup-software

⁠External Referee

External referee has already been downloaded to the home directory (ssl-game-controller_v3.12.3_linux_<architecture>).

By default, external referee serves localhost:8081, which can't be port forwarded to your host machine. Therefore, you need to change the address where external referee is serving. Inside the docker container, the correct command is ./ssl-game-controller_v3.12.3_linux_<architecture> -address 0.0.0.0:8081

You can now use external referee from your host machine at http://localhost:8081/⁠

⁠RQT (UNDER CONSTRUCTION)

1. Download XQuartz (brew install --cask xquartz)
2. XQuartz > Settings > Security > "Allow connections from network clients"
3. Close and restart XQuartz
4. Run export DISPLAY=:0 && xhost +127.0.0.1 in terminal
5. Enter the Docker container and ...

⁠IDE Setup

Modifying the code within the noVNC environment is not recommended. Instead, you should remotely develop on your host machine using VS Code.

You can do so by starting the container and using the remote development extension (https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack⁠) to connect with the container on your host machine.