@parbat101 Since it is included in that image, one (bad) option is to modify the script and then re-build the Docker image and it will pull in the modified script.
The better solution that I would recommend is create a new script i.e my-script.py and then mount it inside the Docker image on run time using something like this:
docker run -it --rm --privileged --net=host -v $(pwd)/my-script.py:/path/to/my-script.py gcr.io/modalai-public/voxl-mavsdk-python:v1.1 /bin/bash
where you mount the script from your host os inside of the Docker container. You can read more about docker + mounting here: https://docs.docker.com/storage/bind-mounts/
This would allow you to modify the script on your host os, then run the above command to pull it into the docker container on run-time. Keep in mind if you modify the script inside of the docker container and then exit the container, the edits will be lost. So make sure you edit the script outside of the container and then re-run the above command to pull in the updated script.
Another note, /path/to/my-script.py will denote the path at which you would like to have the script live inside of the docker container, so you will need to modify that to your liking.
