You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somewhere in the realm of zeek/zeek#2650, the spicy:latest image contains extra zkg state that seems unneeded to ship.
Without optimizing a lot, it seems from the 3.6G payload in the image, we can delete ~2GB of build/test artifacts without functional impact.
This is likely not concretely related to Spicy, but the zkg/spicy-plugin ecosystem. The container is built here, so opening the ticket here for now.
A few observations:
I thought build directories of zkg are ephemeral and deleted afterwards? They seem to linger on in zkg/clones
spicy-plugin is installing {{src}} and {{CMakeFiles}} into /opt/zeek/lib/plugins/ directories that looks like just cmake artifacts
Why isn't /root/.zkg/testing ephemeral
Could we strip .htlo files by default?
This is probably not container specific either, but likely to happen in "production environments" using zkg with spicy-plugin and spicy analyzers, too.
$ docker pull zeekurity/spicy:latest
latest: Pulling from zeekurity/spicy
Digest: sha256:6d7ee8e1985dc9fe620352a836a15bae0c42e9a0817e6605a061e9267fb4491c
Status: Image is up to date for zeekurity/spicy:latest
docker.io/zeekurity/spicy:latest
$ docker run --rm -it zeek/spicy:latest /bin/bash
root@8a51a6f8da71:~# cd /
root@8a51a6f8da71:/# du -d 3 -h | sort -h
...
225M ./usr/lib/locale
230M ./opt/spicy/lib
297M ./opt/spicy
543M ./usr/lib
660M ./usr
778M ./root/.zkg/clones # See below for `build` directories
791M ./opt/zeek/lib # See below for CMakeFiles from spicy-plugin
821M ./opt/zeek
943M ./root/.zkg/testing # This seems not needed
1.3G ./opt
1.7G ./root
1.7G ./root/.zkg
3.6G .
The build directories within the zkg clones should not be needed (not sure why they are actually still around, that might be a bug in zkg).
I am not sure we want to spend a lot of effort optimizing this image as the Zeek container comes with Spicy now. As far as I recall we also do not use it in any of our CI anymore.
Somewhere in the realm of zeek/zeek#2650, the spicy:latest image contains extra zkg state that seems unneeded to ship.
Without optimizing a lot, it seems from the 3.6G payload in the image, we can delete ~2GB of build/test artifacts without functional impact.
This is likely not concretely related to Spicy, but the zkg/spicy-plugin ecosystem. The container is built here, so opening the ticket here for now.
A few observations:
This is probably not container specific either, but likely to happen in "production environments" using zkg with spicy-plugin and spicy analyzers, too.
The build directories within the zkg clones should not be needed (not sure why they are actually still around, that might be a bug in zkg).
The installed spicy-plugin contains CMakeFiles and src:
So, it seems to remove all these artifacts without harm from what I can tell and shrink the unpacked filesystem size from 3.6G to 1.7G.
The text was updated successfully, but these errors were encountered: