Xeol image itself EOL
Closed this issue · 0 comments
m-barthelemy commented
What happened:
Xeol detects its own Docker image as EOL
What you expected to happen:
Xeol uses up to date base image and packages
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
The noqcks/xeol:v0.10.0
image is running on a quite old and now EOL version of Alpine.
So Xeol now detects itself as being end of life :)
Additionally, the image seems to use a version of Golang affected by CVE-2024-24790 and others.
Environment:
- Output of
xeol version
: 0.10.0 - OS (e.g:
cat /etc/os-release
or similar): Alpine Linux 3.17