PIP not working on Spark VENV

[djpirra]

Name and Version

bitnami/spark 3.2.1

What architecture are you using?

None

What steps will reproduce the bug?

If you activate Spark VENV environment and try to run PIP, it gives the below error:

FileNotFoundError: [Errno 2] No such file or directory: '/opt/bitnami/spark/venv/lib/python3.8/site-packages/pip/_vendor/certifi/cacert.pem'

What is the expected behavior?

PIP should work as expected.

What do you see instead?

FileNotFoundError: [Errno 2] No such file or directory: '/opt/bitnami/spark/venv/lib/python3.8/site-packages/pip/_vendor/certifi/cacert.pem'

[Mauraza]

Hi @djpirra,

Could you test with the last revision of 3.2?

$ docker images
REPOSITORY      TAG       IMAGE ID       CREATED        SIZE
bitnami/spark   3.2       61045d010dec   29 hours ago   1.35GB

[djpirra]

I was using this one: docker.io/bitnami/spark:3.2.1

Which one is it now?

[Mauraza]

Hi @djpirra,

The last revision: docker pull bitnami/spark:3.2.4-debian-11-r141

[djpirra]

Hi Ibone,

I am bounded to 3.2.1 since that is the latest runtime that Oracle Dataflows supports.

Thank you

On Wed, 27 Sep 2023 at 13:55 Ibone González Mauraza < @.***> wrote:

Hi @djpirra https://github.com/djpirra,

The last revision: docker pull bitnami/spark:3.2.4-debian-11-r141

— Reply to this email directly, view it on GitHub https://github.com/bitnami/containers/issues/49313#issuecomment-1737082637, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADZ5Q5SSYFAM5HGQTJUMBDTX4PZ2NANCNFSM6AAAAAA5AOWIPQ . You are receiving this because you were mentioned.Message ID: @.***>

[Mauraza]

Hi @djpirra,

You can check if exits any revision that works. Check https://hub.docker.com/r/bitnami/spark/tags?page=1&name=3.2.1

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions[bot]]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.