The docker image gns3/kalilinux didn't work well with the docker build tool. As the base image is build every week, the build tool would normally run a rebuild every week. By setting the base image to NONE in docker/docker_images, the check for a changed base image was disabled. But that requires, that the gns3 devs need to manually monitor kalilinux for important changes and then run the build tool manually. That is not optimal.
This PR wants to change that. First it uses kalilinux/kali-last-release as the base image, which changes only quarterly when a new kali release is published. But nevertheless this base image is rebuild every week. So I added a check in the workflow for a changed version, which will trigger a forced rebuild of kalilinux.
Before submitting a pull request, please check the following.
When updating an existing appliance:
[ ] The new version is on top.
[ ] The filenames in the "images" section are unique, to avoid appliances / version overwriting each other.
[x] If you forked the repo, running check.py doesn't drop any errors for the updated file.
The docker image gns3/kalilinux didn't work well with the docker build tool. As the base image is build every week, the build tool would normally run a rebuild every week. By setting the base image to NONE in
docker/docker_images, the check for a changed base image was disabled. But that requires, that the gns3 devs need to manually monitor kalilinux for important changes and then run the build tool manually. That is not optimal.This PR wants to change that. First it uses kalilinux/kali-last-release as the base image, which changes only quarterly when a new kali release is published. But nevertheless this base image is rebuild every week. So I added a check in the workflow for a changed version, which will trigger a forced rebuild of kalilinux.
Before submitting a pull request, please check the following.
When updating an existing appliance:
[x] If you forked the repo, running check.py doesn't drop any errors for the updated file.