GitLab

Our VS Code devcontainer is based on our buildenv container, so we directly modify the latter.

This temporarily drops support for DDIO and the L3 cache.

Before this, if registry or tag got set, we would still build all images
starting from the docker hub regsitry version and latest tag.

This makes it easier for images that build on ours to use tools like packer
without having to specify the full path

Update to newer ns-3 version and adapt code for changes (mostly
renamed files and command line parameters) in the ns-3 submodule.

Add a cleanup script for ns-3 similar to those for qemu and gem5.

This solves #9.

When we switched to a newer kernel version in c64d3d0e, the
cleanup_images.sh script no longer removed the linux kernel source
folder, since it still used the old version number. Now, I use a regex
to avoid this issue in the future.

This will push the images built by docker-images and docker-images-debug
target, if they exist.

This will result in make docker-images directly generating images with
appropriate tags.

simbricks/simbricks additionally with gem5.opt installed in addition to
gem5.fast. About 1.1GB larger.

(this image takes very long to build)

increases connection limits, disables host fingerprint checking, enables persistent connections