Updating base images from slim-buster to slim-bullseye

[pradeepp88]

Creating this PR to update the base docker images from slim-buster to slim-bullseye version as the slim-buster image is reported to have known vulnerabilities identified by scanning tools like Snyk and Qualys. This relates to #2087 where this is discussed.

Signed-off-by: pradeepp88 [email protected]

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[pradeepp88]

@WadeBarnes thanks for running the tests. It looks like the integration tests are failing, does this have to do anything with the base Docker images? I see that they are being built from Dockerfile.demo and Dockerfile.bdd, do we need to update them? Please let me know, thanks.

[swcurran]

Any ideas on the integration test? @ianco — is this an intermittent failure? Do you have a list of tests that fail intermittently so that we can both try to improve them, and know when it is a real failure vs. an intermittent one? Perhaps a doc file we can reference in the repo?

[WadeBarnes]

The failing tests have nothing to do with the changes made here. I've restarted them to see if it's just and intermittent issue.

[WadeBarnes]

It was an intermittent failure.

[ianco]

FYI I can run ./scripts/run_tests but if I try ./scripts/run_tests_indy I get an error:

failed to solve with frontend dockerfile.v0: failed to create LLB definition: docker.io/library/python:3.6.13-slim-bullseye: not found

... which is weird because when I run ./scripts/run_tests I see this in the log:

 => [internal] load metadata for docker.io/library/python:3.6.13-slim-buster                                                                                                                                       0.7s
 => [1/6] FROM docker.io/library/python:3.6.13-slim-buster@sha256:c2799d37ac08bcf4c6214e2196b43801acbf90334f565944c4e8b994ed7f7956                                                                                 0.0s

(ok I guess it's not weird, one is using buster and one is trying to use bullseye ...)

[ianco]

FYI I can run ./scripts/run_tests but if I try ./scripts/run_tests_indy I get an error:

If I set PYTHON_VERSION=3.19.6 then it can pull the bullseye image ... @pradeepp88 @WadeBarnes

Not sure what python version we should be targetting?

[WadeBarnes]

@ianco, Python 3.9, and 3.6 for legacy.