Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upUnsupported Event - container exec_die #2717
Open
Comments
|
same thing here: for every container that has a HEALTHCHECK built in I get three events every second - one of them unsupported. makes the event log basically useless since it is full of white noise. |
|
Yes, same here as well... |
|
Anyone know how to fix this issue? |
|
I believe it's just about adding a new case in the following model: https://github.com/portainer/portainer/blob/develop/app/docker/models/event.js |
|
Same here as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Moby added an exec_die container event a little over a year ago in f97256cbf1 via PR35744 (cherry-picked to docker-ce 18.03 via 27f91f80b9). The event reports a
docker execexit code, including HEALTHCHECK executions, and denotes that the executed command has completed. Portainer currently shows this as an Unsupported Event.Is your feature request related to a problem? Please describe.
There's no immediate problem at issue. It is merely unclear when 1/3 events are displayed as
Unsupported Event, and it's unclear if thedocker execinstance encountered an error.Describe the solution you'd like
Add support to Portainer for displaying the container exec_die event, preferably displaying the exit code, or a Success/Failure message, or similar.
Describe alternatives you've considered
Reducing the container's HEALTHCHECK interval to see fewer
Unsupported Evententries.Additional context

Portainer 1.20.1 shows the following event log:
In plain-text:
While
docker events --since 30sshows: