Docker unable to import trasnceiver_pb2 about starlink-grpc-tools HOT 2 CLOSED

This is likely the result of the dish software adding one or more new protocol files to the gRPC service. I noticed there were some new request messages listed in SpaceX.API.Device.Request.

The docker container pulls the protocol data dynamically when it starts up and only pulls the files it knows about. While we don't need anything in the new protocol files, the top-level one defining the service still imports them, so will fail if they are missing.

I'm working on getting reflection working directly in the Python scripts, which will eliminate the need for this, but in the mean time, we can just add the new proto files. I'll have a look tomorrow morning and update the instructions in the README and I can update entrypoint.sh so the docker container starts running the new instructions, but @neurocis will need to update the published image.

from starlink-grpc-tools.

It looks like the published image has been updated with this change, so this issue should now be resolved. I did also update the README, as this would affect running outside of docker as well, the next time someone ran (or reran) the protoc commands.

from starlink-grpc-tools.