The build hooks documentation states that…
To override these phases, create a folder called
hooksin your source code repository at the same directory level as your Dockerfile.
I am working on a repository with multiple Dockerfiles and we want to automate tag generation with build hooks (see issue on GitHub).
On Docker Hub, does the build context influence where the hooks directory is expected?
In other words: In a repository with 10+ Dockerfiles all using the same
post_build hook, can we safe the duplication of said hook file on Docker Hub?