Skip to content

Xeol image itself EOL #422

@m-barthelemy

Description

@m-barthelemy

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions