Workflow caching ineffective #3
Description
The cache_froms lines in the github wrokflow is meant to speed up building by allowing docker to use the cache. However, this run should not have busted the cache and caused a full Zeek rebuild, but it did.
My current suspicion is that because we are using a multi-stage build the layers from the first stage are not being pushed to the docker repository and thus can't be used for caching. Look into the target config to see if we can push the builder stage to Dockerhub (e.g. activecm/zeek:builder) and then add that tag to the cache_froms config line.