-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RHOAIENG-11349] - Missing requirements.txt for modelmesh-runtime-adpter component #65
[RHOAIENG-11349] - Missing requirements.txt for modelmesh-runtime-adpter component #65
Conversation
c4ffae9
to
0d8771b
Compare
c8ddd76
to
5fed933
Compare
Moved red-hat-data-services#23 to here. |
fe970c8
to
dbf991c
Compare
/test images |
5654610
to
7367985
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One additional change...
Dockerfile
Outdated
pip install wheel && \ | ||
pip install grpcio && \ | ||
# pin to 3.10.0 to avoid error: libhdf5.so: cannot open shared object file: No such file or directory \ | ||
# if not version is set, it will install the 3.11.0 version which, seems that does not have the h5py dependencies \ | ||
# for arm yet. | ||
pip install h5py==3.10.0 && \ | ||
pip install tensorflow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace all these pip install
commands with a single pip install -r requirements.txt
one and then I will be happy to approve.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agreed with @israel-hdez . However, if we replace this, we should update the requirements.txt file when the version changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right, I've forget to do this, I've added the requirements file inside the container but forgot to install from it
…pter component chore: Add the requirements.txt file and steps to generate it and correctly configure the Konflux build. Plus, adapt the Dockerfile to work properly witn Konflux. Signed-off-by: Spolti <fspolti@redhat.com>
7367985
to
5b1401d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: israel-hdez, spolti The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@spolti will you cherry-pick to 0.12 branch? or is this only for main? |
7d59320
into
opendatahub-io:main
The plan is only for main, but we can cherry-pick later. |
…pter component (opendatahub-io#65) chore: Add the requirements.txt file and steps to generate it and correctly configure the Konflux build. Plus, adapt the Dockerfile to work properly witn Konflux. Signed-off-by: Spolti <fspolti@redhat.com>
…pter component (opendatahub-io#65) chore: Add the requirements.txt file and steps to generate it and correctly configure the Konflux build. Plus, adapt the Dockerfile to work properly witn Konflux. Signed-off-by: Spolti <fspolti@redhat.com> Signed-off-by: mholder6 <marholde@redhat.com>
…pter component (#65) chore: Add the requirements.txt file and steps to generate it and correctly configure the Konflux build. Plus, adapt the Dockerfile to work properly witn Konflux. Signed-off-by: Spolti <fspolti@redhat.com> Signed-off-by: mholder6 <marholde@redhat.com>
chore: Adapt Dockerfile to work on Konflux.
Motivation
Modifications
Result