log4pot fails to pull docker image.

[JeffMcGeoff]

As the title reads, log4pot docker image fails to pull from "ghcr.io/telekom-security/log4pot:24.04.1" which subsequently redirects to "https://github.com/telekom-security/tpotce/pkgs/container/log4pot" as there is no log4pot image tagged with "24.04.1". This gives the error manifest unknown when pulling the log4pot docker image.

This is also evident in "docker/log4pot/docker-compose.yml" where on line 23 image: "dtagdevsec/log4pot:24.04" was replaced with image: "ghcr.io/telekom-security/log4pot:24.04.1".

Since all .yml files use the version variable ${TPOT_VERSION}, it defaults to 24.04.1 when pulling images. Within the docker-compose.yml file, manually changing to a valid image version works as intended and the image is successfully pulled from "https://github.com/telekom-security/tpotce/pkgs/container/log4pot".

[t3chn0m4g3]

Thanks for reporting. We are investigating this currently as multi-arch builds are currently broken when building log4pot. It seems some dependencies will no longer built using qemu (on x64) and we are now identifying the responsible packages.

[t3chn0m4g3]

@JeffMcGeoff Just pushed the images, works fine on our end.

[JeffMcGeoff]

Thank you @t3chn0m4g3, I can confirm log4pot docker image is successfully pulled from the repo when I deployed tpot earlier today with a customised docker-compose.yml file.

[t3chn0m4g3]

Great to hear! Thanks for the feedback!