Justin

I have some commits here that help a bit: https://github.com/zeek/package-manager/compare/master...JustinAzoff:package-manager:faster-bundles There were a few simple optimizations that could be made to speed up the git bits. I also found that...

Cool! it's not a totally full fix, but changing the process of building bundles to cloning all repositories across the manifests, then rewriting the manifests to use the local clones...

@ckreibich Did you check if packages only had a bro-pkg.meta or both a bro-pkg.meta and a zkg.meta? I know a few of mine probably have both, and the bro-pkg.meta was...

Can you share what you are trying to do using zeekctl inside of the container? I've been meaning to remove it entirely since it usually doesn't make sense in a...

https://docs.zeek.org/en/current/frameworks/supervisor.html is what should be used for running zeek in a container

yeah.. I know.. I'm torn about what to do about this. just removing the zeekctl bits would simplify the container a bit... and using zeekctl inside of a container is...

Ah, I never actually tried using broctl in the container - but I can swap out python-minimal for python2.7. This likely affects all of the images, not just 2.5.5

multistage docker files are being used now, still need to use build args which will mean most files can be removed https://docs.docker.com/engine/reference/builder/#arg

The main thing is using --build-args so one could easily just pass in 3.0.1, 3.0.2, 3.0.3, 3.1.0, 3.1.1 and have it build the image without having to have 5 dockerfiles....

Yeah, we should be using debian buster now, not stretch. having a common zeek-builder base image is a great idea too.