RHAIENG-2114: Added --allowerasing to dnf install to fix the conflict… #1737
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was conflicting version of packages provided by UBI9 vs. RHEL EUS s390x repos. I propose this fix here by adding --allowerasing to erase/replace those conflict packages.
You can test this locally here:
podman build -f jupyter/datascience/ubi9-python-3.12/Dockerfile.konflux.cpu --platform linux/s390x -t jupyter-datascience-ubi9-s390x --build-arg BASE_IMAGE=quay.io/aipcc/base-images/cpu:3.0-1761580156 .Description
Add --allowerasing to dnf install
How Has This Been Tested?
Self checklist (all need to be checked):
make test(gmakeon macOS) before asking for reviewDockerfile.konfluxfiles should be done inodh/notebooksand automatically synced torhds/notebooks. For Konflux-specific changes, modifyDockerfile.konfluxfiles directly inrhds/notebooksas these require special attention in the downstream repository and flow to the upcoming RHOAI release.Merge criteria: