Sitelet https://web.archive.org/web/20200902200924/https://github.com/portainer/portainer/issues/2717
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unsupported Event - container exec_die #2717

Open
phroggster opened this issue Feb 15, 2019 · 5 comments
Open

Unsupported Event - container exec_die #2717

phroggster opened this issue Feb 15, 2019 · 5 comments

Comments

@phroggster
Copy link

@phroggster phroggster commented Feb 15, 2019

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 exec exit 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 the docker exec instance 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 Event entries.

Additional context
Portainer 1.20.1 shows the following event log:
unsupported event
In plain-text:

Date Category Details
2019-02-15 17:12:13 container Exec instance created
2019-02-15 17:12:13 container Exec instance started
2019-02-15 17:12:14 container Unsupported event

While docker events --since 30s shows:

2019-02-15T17:12:13.936857056Z container exec_create: /bin/sh -c /usr/local/bin/docker-healthcheck.sh || exit 1 f95b731a43db47cc2021079cc73f764c4884877508faf9e05aea6f3ca776ef82 (com.docker.compose.config-hash=3381614071d2645883f98a706a0ee30e10813b68341226db4f81ba57f2092735, com.docker.compose.container-number=1, com.docker.compose.oneoff=False, com.docker.compose.project=unifi, com.docker.compose.service=controller, com.docker.compose.version=1.23.2, execID=9551142e710462ba5abb658b0e8ec1aba7493b8e5b951aece21dc918158ef70b, image=unifi_controller, maintainer=Jacob Alberty <jacob.alberty@foundigital.com>, name=unifi_controller_1)
2019-02-15T17:12:13.936904975Z container exec_start: /bin/sh -c /usr/local/bin/docker-healthcheck.sh || exit 1 f95b731a43db47cc2021079cc73f764c4884877508faf9e05aea6f3ca776ef82 (com.docker.compose.config-hash=3381614071d2645883f98a706a0ee30e10813b68341226db4f81ba57f2092735, com.docker.compose.container-number=1, com.docker.compose.oneoff=False, com.docker.compose.project=unifi, com.docker.compose.service=controller, com.docker.compose.version=1.23.2, execID=9551142e710462ba5abb658b0e8ec1aba7493b8e5b951aece21dc918158ef70b, image=unifi_controller, maintainer=Jacob Alberty <jacob.alberty@foundigital.com>, name=unifi_controller_1)
2019-02-15T17:12:14.237065107Z container exec_die f95b731a43db47cc2021079cc73f764c4884877508faf9e05aea6f3ca776ef82 (com.docker.compose.config-hash=3381614071d2645883f98a706a0ee30e10813b68341226db4f81ba57f2092735, com.docker.compose.container-number=1, com.docker.compose.oneoff=False, com.docker.compose.project=unifi, com.docker.compose.service=controller, com.docker.compose.version=1.23.2, execID=9551142e710462ba5abb658b0e8ec1aba7493b8e5b951aece21dc918158ef70b, exitCode=0, image=unifi_controller, maintainer=Jacob Alberty <jacob.alberty@foundigital.com>, name=unifi_controller_1)
@lemmy04
Copy link

@lemmy04 lemmy04 commented Jan 25, 2020

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.

@m4tt075
Copy link

@m4tt075 m4tt075 commented Feb 10, 2020

Yes, same here as well...

@ozdeadmeat
Copy link

@ozdeadmeat ozdeadmeat commented May 20, 2020

Anyone know how to fix this issue?

@deviantony
Copy link
Member

@deviantony deviantony commented May 20, 2020

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

@itsconquest itsconquest self-assigned this Jun 15, 2020
@olonsoft
Copy link

@olonsoft olonsoft commented Jun 22, 2020

Same here as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants
You can’t perform that action at this time.