change google to debian, add docker-compose file

[albjeremias]

yellow! :)

[theSuess]

Hey there, thanks for the PR.

What's the advantage of using the debian image instead of the distroless one?

[albjeremias]

Well is just that I don't trust google at all to control any of the circuits i am. The only advantage is that for now.
But maybe the more sense would be to use the official go image?
https://hub.docker.com/_/golang/

anywayz.. my fight against google is political also.. check out: https://wiki.fuckoffgoogle.de

[theSuess]

If you want to swap the image for something non-google I'd go with either redhat ubi or just FROM scratch. Distrust does not need any external libraries so this should not be an issue.

[albjeremias]

why no golang? its probably the leightest... even though i dont have big concerns with any of those. but just to keep it simple.

[theSuess]

The golang image contains the entire go toolchain. We do not have any runtime dependencies, so we can just skip this

[pzhlkj6612]

Suggested change

	Generate a new key: `docker-compose exec distrust ./distrust genkey`
	Generate a new key: `docker-compose exec distrust genkey`

We already have ENTRYPOINT ["/distrust"] in Dockerfile, so the container itself is a "distrust" and we should call it directly, like this:

# docker run -it --rm ghcr.io/parkour-vienna/distrust:master genkey
-----BEGIN RSA PRIVATE KEY-----
...

Ref: https://docs.docker.com/reference/dockerfile/#entrypoint