Docker: additional_logs adds old log

[Knight1]

The Dockerfile just copies over the config.sample.yaml as config.yaml

certstream-server-go/Dockerfile

Line 20 in 8d71967

COPY ./config.sample.yaml /app/config.yaml

This now results in the nessie2022 mirror being in the log list besides this one no longer in the Chrome CT List and the Log is no longer reachable thus no certs to monitor.
https://issues.chromium.org/issues/41364542#comment56

[d-Rickyy-b]

Hi there and first of all thanks for your effort.

The Dockerfile just copies over the config.sample.yaml as config.yaml

Exactly. That's to have some default config for the server in order to not fail upon starting for the first time.

[...] besides this one no longer in the Chrome CT List

Yes, that is the point of the "additional logs" section of the config. To add custom logs or logs that aren't in the Chrome CT list.

[...] and the Log is no longer reachable [...]

That can definitely be changed to a more recent log. But let's not forget that this is just the sample config file. While it is included in the docker image, it is supposed to get changed by the user.

Currently I see two ways on how to go from here:

1. Add another default config next to the sample config that gets included in the docker image instead
2. Don't include any config in the container and exit with an error, if a config file isn't present (aka not mounted via a docker volume)

---

Apart from that, I see the need to be able to set the configuration for the container via environment variables. This could prove especially useful for kubernetes clusters but also for having everything you need to run the server in a single docker-compose.yml instead of an additional config yml. So I created #67 to track this. As soon as I find the time to implement that, we could easily go with 2) and add some sane default settings to the docker-compose.yml and explain the settings better on the relevant wiki page.