Closed x-Felix closed 3 years ago
Why not let the container run on 53 and just expose another port publicly? -p 5353:53
Otherwise, update the Docker file and rebuild or rely on something like Prometheus.
On Fri, Sep 11, 2020, 7:26 AM Felix notifications@github.com wrote:
HEALTHCHECK --interval=5s --timeout=3s --start-period=5s CMD drill @ 127.0.0.1 cloudflare.com || exit 1
If unbound.conf is set to use non 53 port, container healthcheck will always show unhealthy. Is there better way to check the service status?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/MatthewVance/unbound-docker-rpi/issues/6, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUMHOS56VVN3DSAJ7AQD2TSFIJQLANCNFSM4RHLZZLA .
I use docker-compose.yml to disable healthcheck for this container. I don’t want it keeps query Cloudflare.
healthcheck: disable: true
HEALTHCHECK --interval=5s --timeout=3s --start-period=5s CMD drill @127.0.0.1 cloudflare.com || exit 1
If unbound.conf is set to use non 53 port, container healthcheck will always show unhealthy. Is there better way to check the service status?