Drop namely/protoc-all in favour of a custom Dockerfile?

[kommendorkapten]

When working on #112 I realised that the namely/protoc-all seems to be closed source, and it's very old (Debian Bullseye) which as an example lacks a new Go toolkit (only provides 1.15, released 2021).

It wasn't that hard to hack together a Docker image based on Alpine with rudimentary support for protoc. I think it would be worth exploring the work for adding Java, Ruby and other languages to make sure we know what's get into the image, and are not locked to a closed sourced vendor. As an example, I had to craft a new Docker image with newer Go version to be able to get the JSON schema generation to work.

cc @woodruffw @haydentherapper @znewman01

[woodruffw]

+1 from me -- IMO having our own (non-closed) container would be a transparency and dependency quality win for us 🙂

[haydentherapper]

That’s good with me. We will use it in fulcio too, since we have to compile proto for grpc.

[jalseth]

+1. We should consider using the buf CLI which is more ergonomic to use than upstream protoc CLi.

https://buf.build/docs/ecosystem/cli-overview