tree 213185958a06d46c98b202816beb9ec28a917855
parent 606a90995f826685fc3fdc6af9cafc9e59abcf8a
author Marc Kupietz <kupietz@ids-mannheim.de> 1785461470 +0900
committer Marc Kupietz <kupietz@ids-mannheim.de> 1785461470 +0900

CI: modernize the docker slimming

Follows what Kalamar does. slimtoolkit became mintoolkit, and the invocation
had to change anyway: the tool has no --in-container option anymore, so the
job would have stopped at an unknown flag. The download of the slim binary
goes away with it, it was never used, the containerized tool was called
instead.

FF_NETWORK_PER_BUILD and the dns option of the dind service let the mint
container reach the container it probes, as in Kalamar.

The probe waited 10 seconds for the server, which is not enough: the image
compiles its Inline C at startup and then loads the model, and only answers
after 21 seconds, measured with the image of this commit. It waits 60 now.

The image tarball carries the version in its name, as in Kalamar, and
upload-docker was adapted accordingly. It only runs for v tags now and has to
be started by hand. Before it also ran for every master commit, where
CI_COMMIT_TAG is empty and it would have pushed a tag-less image.

The .dockerignore did not catch .gitlab-ci-local, it was written with a dot
instead of a hyphen. Everybody who runs gitlab-ci-local and then builds the
image locally packed the whole CI scratch directory into it, 549 MB in my
case, including job logs, which contain the CI variables. Release tarballs are
ignored now, too. This does not affect images built in CI, whose checkout is
clean.

Verified locally by running the whole chain: the large image builds, mint
minifies it from 1.3 GB to 905 MB with the http probe answering 200, and the
image from Dockerfile.remove-example-data serves neighbours, collocators and
getVecsByRanks correctly with the compilers removed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Change-Id: I0014c8d2e4f4cee667b0d1c5016f037c9aa44743