arvindKandpal-ksolves opened a new pull request, #4631:
URL: https://github.com/apache/cassandra/pull/4631

   ### Description
   This PR fixes the build failures for the `cqlsh` Docker environments in the 
`pylib` directory. The previous use of `ubuntu:bionic` (18.04) was causing 
build errors because it is End-of-Life (EOL) and does not natively support the 
required Python versions (3.8 - 3.11).
   
   ### Changes
   * **pylib/Dockerfile.ubuntu.py3**: Upgraded base image from `ubuntu:bionic` 
to `ubuntu:focal` (20.04) and updated the Python link to use the default Python 
3.8.
   * **pylib/Dockerfile.ubuntu.py38**: Upgraded base image to `ubuntu:focal` to 
ensure native support for Python 3.8-minimal.
   * **pylib/Dockerfile.ubuntu.py311**: Upgraded base image to `ubuntu:jammy` 
(22.04) and added the `deadsnakes/ppa` repository to install Python 3.11. 
   
   ### Reproduction of Issue
   Prior to these changes, running the following commands resulted in errors 
such as `Unable to locate package python3.11-minimal` or `alternative path 
/usr/bin/python3.8 doesn't exist`:
   `docker build . -f pylib/Dockerfile.ubuntu.py3 -t test-py3`
   
   ### Testing
   I have locally verified that all three Dockerfiles build successfully using 
the following commands:
   1. `docker build . -f pylib/Dockerfile.ubuntu.py3 -t test-py3`
   2. `docker build . -f pylib/Dockerfile.ubuntu.py38 -t test-py38`
   3. `docker build . -f pylib/Dockerfile.ubuntu.py311 -t test-py311`
   
   All builds now complete successfully without manual intervention.
   
   patch by arvindksi274; for CASSANDRA-20181


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to