Trivy scan errors with pyenv installation in Dockerfile

[AshwinSridharan0410]

This is my dockerfile
RUN curl https://pyenv.run | bash
ENV PYENV_ROOT="/root/.pyenv"
ENV PATH="$PYENV_ROOT/bin:$PYENV_ROOT/shims:$PATH"
RUN echo 'eval "$(pyenv init --path)"' >> /root/.bashrc
RUN pyenv install 3.7.17
&& pyenv install 3.8.18
&& pyenv install 3.9.18
&& pyenv install 3.10.13
&& pyenv install 3.11.5
RUN pyenv versions
RUN pyenv global 3.7.17 3.8.18 3.9.18 3.10.13 3.11.5

My base image is clean and doesn't have any vulnerabilities

When I execute this command below:-
trivy image --severity HIGH,CRITICAL --ignore-unfixed image_name

I am getting these vulnerabilities:-

Thanks

[native-api]

These are old releases and naturally, they have older versions of libraries bundled.

(See Status of Python versions) 3.7 is EOL so it's unpatched. We can accept a patch PR with a fix from an interested party.
3.8+ seem to have the fix in the latest releases.

[native-api]

So as per above, I'm not sure what you expect us to do.

[AshwinSridharan0410]

@native-api , my requirement is to install multiple versions of python inside a docker image. For that reason, I used pyenv and when I scan my image with trivy , it was giving me these vulnerabilties. So , was unsure what to do

Even if I use 3.8 and the above versions, I am getting this issue .

Hope my requirement is clear. Also ,can you suggest me to achieve my requirement in a different approach , if there are any ?
Thanks

[native-api]

You can upgrade setuptools after installation.

In fact, since 3.4, CPython's build is supposed to do that itself during the build.

Then, unless you require specific micro versions, you can pyenv install 3.8 etc to get the latest release in the version line.
since 2.3.30, you can also pass multiple versions to pyenv install.