canonical / cos-alerter

Receive regular pings from the COS stack and alert when they are not arriving in a timely fashion.
Apache License 2.0
1 stars 1 forks source link

Container keeps running if cos-alerter fails. #38

Closed dstathis closed 6 months ago

dstathis commented 1 year ago

Bug Description

When running the rock, if cos-alerter fails, the container continues to run with no indication that anything is wrong.

To Reproduce

docker run -p 8080:8080 ghcr.io/canonical/cos-alerter:latest Note that no config file is mounted here so cos-alerter fails. There is however no indication.

Environment

$ docker --version
Docker version 20.10.17, build 100c70180f

Relevant log output

$ docker run -p 8080:8080 ghcr.io/canonical/cos-alerter:latest
2023-04-25T11:17:49.382Z [pebble] Started daemon.
2023-04-25T11:17:49.390Z [pebble] POST /v1/services 6.966668ms 202
2023-04-25T11:17:49.390Z [pebble] Started default services with change 1.
2023-04-25T11:17:49.397Z [pebble] Service "cos-alerter" starting: /usr/bin/cos-alerter

Note: cos-alerter has already failed here.

Additional context

No response