Closed jbusche closed 3 months ago
I deployed the image with a pytorchjob on a FIPS OC 4.16.2 cluster, and it succeeded:
oc get pytorchjobs,pods -n default api.jim416fips.cp.fyre.ibm.com: Wed Aug 7 09:46:05 2024
NAME STATE AGE
pytorchjob.kubeflow.org/ted-kfto-sft Succeeded 19m
NAME READY STATUS RESTARTS AGE
pod/ted-kfto-sft-master-0 0/1 Completed 0 19m
and the image:
oc describe pod -n default |grep Image;
Image: quay.io/jbusche/fms-hf-tuning:jim-updatesetuptools
Image ID: quay.io/jbusche/fms-hf-tuning@sha256:345be77ff52f70eebc3de98507d9e57cdcb62c2e9fe66efad40f1ab6ae7e4098
Description of the change
I'm noticing a high security vulnerability with setuptools.
So I'm adding a line to the DockerFile to force an update to setuptools.
Related issue number
Closes 1176 https://github.ibm.com/ai-foundation/watson-fm-stack-tracker/issues/1176
How to verify the PR
I clone my branch:
Then I build the image:
and I get:
Successfully tagged localhost/fms-hf-tuning:jim-updatesetuptools
Now I can run the image locally and look at the setuptools version:
I also used Twistlock to scan the image and it came up clean for setuptools.
Was the PR tested