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

Docker Build event #15211

Open
FrenchBen opened this Issue Jul 31, 2015 · 5 comments

Comments

Projects
None yet
7 participants
@FrenchBen
Contributor

FrenchBen commented Jul 31, 2015

It doesn't seem that docker build triggers any event - Could we get a build event triggered when it completes?
Maybe something like:
daemon.eventsService.Log("build", logName, "")

The doc doesn't seem to hint at the above being triggered:
https://github.com/docker/docker/blob/master/docs/reference/api/docker_remote_api_v1.21.md#monitor-dockers-events

For example run docker events in a terminal and pull an image docker pull elyase/staticpython - The events will be:

2015-07-31T17:45:53.000000000-04:00 elyase/staticpython:latest: pull

Now keeping the same docker events terminal open, build an image: docker build -t staticpy . downloaded from https://github.com/elyase/docker.git
The events in the other terminal are empty, aka still showing only the previous pull:

2015-07-31T17:45:53.000000000-04:00 elyase/staticpython:latest: pull
@duglin

This comment has been minimized.

Contributor

duglin commented Jul 31, 2015

seems reasonable - #dibs

@duglin duglin self-assigned this Jul 31, 2015

@FrenchBen

This comment has been minimized.

Contributor

FrenchBen commented Jul 31, 2015

👍

duglin added a commit to duglin/docker that referenced this issue Jul 31, 2015

Adds a "build" event
Closes moby#15211

Signed-off-by: Doug Davis <dug@us.ibm.com>

duglin added a commit to duglin/docker that referenced this issue Aug 1, 2015

Adds a "build" event
Closes moby#15211

Signed-off-by: Doug Davis <dug@us.ibm.com>

@jessfraz jessfraz removed the status/claimed label Sep 8, 2015

@icecrime

This comment has been minimized.

Contributor

icecrime commented Sep 10, 2016

Somebody should carry #15216 as the builder is not going anywhere.

@thaJeztah

This comment has been minimized.

Member

thaJeztah commented Sep 23, 2016

PR is opened here; #26545

@funkyfuture

This comment has been minimized.

funkyfuture commented Feb 27, 2017

thanks @FrenchBen for caring about this issue.

would the build event have an id that can be used to identify subsequenct container creation?
my use-case is to simply filter out container events related to image builds. therefore i'd also need to get notified when a build is finished regardless its status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment