[APP-3453] Add python unbuffered environment variable

[ben-cutler-datarobot]

This repository is public. Do not put here any private DataRobot or customer's data: code, datasets, model artifacts, .etc.

The way docker containers run python makes

print("my-statement-here")

Causes the print statements to not show up in the DataRobot logging APIs (eg /api/v2/customApplications/<id>/logs/ )
docker-library/python#604

We could make customers run:

print('my-statement-here', file=sys.stderr)

but that would be a clunky solution.

We can add the environment variable PYTHONUNBUFFERED to the containers.

Summary

Rationale

[engprod-2]

The Needs Review labels were added based on the following file changes.

Team @datarobot/applications (#applications) was assigned because of changes in files:

public_dropin_environments/python312/Dockerfile
public_dropin_environments/python39_streamlit/Dockerfile

Team @datarobot/buzok (#buzok) was assigned because of changes in files:

public_dropin_environments/python311_genai/Dockerfile

Team @datarobot/codegen (#scoring-code) was assigned because of changes in files:

public_dropin_environments/python311_genai/Dockerfile

Team @datarobot/custom-models (#custom-models) was assigned because of changes in files:

public_dropin_environments/python312/Dockerfile
public_dropin_environments/python39_streamlit/Dockerfile

If you think that there are some issues with ownership, please discuss with C&A domain at #core-backend-domain slack channel and create PR to update DRCODEOWNERS\CODEOWNERS file.

[engprod-2]

Label Needs Review: Scoring Code was removed because @shopin32 is part of Scoring Code domain.

[klichukb]

I was right about to do this for all environments. Can I ask you to add this to others as well?

[elatt]

I agree, it seems like there is no reason to not set this in Dockerfile where isatty() is not reliable (https://bugs.python.org/issue41449).

However, we may get more bang for our buck if we update the envs in https://github.com/datarobot/datarobot-user-models/tree/master/docker and then update any envs that don't extend those base images.

[klichukb]

Makes sense to update the base image and also exceptions if they dont inherit from the base.

@ben-cutler-datarobot thank you for the PR, would you be up for this job?

[ben-cutler-datarobot]

Sure thing

[klichukb]

Thanks a lot!
I think we can introduce to the listed python-aware base dropins. @yakov-g can you please assist with publishing new versions of the base image to our dockerhub?

[klichukb]

There are several base images, at least dropin-env-base and dropin-env-base-jdk are used in several of our environments.

[ben-cutler-datarobot]

Ah, I didn't realize the jdk one had python. Got it as well.

[yakov-g]

PLease don't merge, I'll add into one more base image.

[yakov-g]

Added, can merge

[yakov-g]

Hold on again.
I'll update drum and image tag in the base envs

[yakov-g]

Done.
I'll run piplelines to publish base images.
When I worked on those pipelines I did all the testing, but never published new ones. So I'll do this.