IBM Fully Homomorphic Encryption Toolkit For Linux. This toolkit is a Linux based Docker container that demonstrates computing on encrypted data without decrypting it! The toolkit ships with two demos including a fully encrypted Machine Learning inference with a Neural Network and a Privacy-Preserving key-value search.
MIT License
1.43k
stars
158
forks
source link
Deploy To Hyper Protect script, if IBM Cloud user has max 1 image in registry, script returns different error #152
Describe the bug
When using deploy to hyper protect script, and trying to add another image to a ibm cloud registry that already has one, in the case where the user has a max 1 account, the error is this...
`Initializing signed repository for us.icr.io/fhe-hpvs-789-user/fhe-toolkit-fedora-s390x...
unable to reach trust server at this time: 403.
Failed to add signer to: us.icr.io/fhe-hpvs-789-user/fhe-toolkit-fedora-s390x
FATAL: Failed to initiate repository 'us.icr.io/fhe-hpvs-789-user/fhe-toolkit-fedora-s390x' in notary`
This should be replaced with a proper error. I am not certain that we are getting the proper error back from ibm cloud. Most likely we are just passing back the error messaging from ibmcloud to the user, however I think there needs to be some intercepting on our part to make it more user friendly.
To Reproduce
Steps to reproduce the behavior:
Run the script, add an image to your ibm cloud free or ibm employee account
Re-run the script
Script fails with the above error jibberish
Expected behavior
It should tell you that your account can only handle one image at a time, unless you upgrade
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Host Info (The machine hosting the FHE Toolkit Docker container), please provide the output of running the following commands in a termina window:
uname -
ulimit -a
Docker version (run docker -v in Terminal):
Toolkit platform (Fedora, CentOS, Ubuntu):
Additional context
Add any other context about the problem here.
Describe the bug When using deploy to hyper protect script, and trying to add another image to a ibm cloud registry that already has one, in the case where the user has a max 1 account, the error is this...
This should be replaced with a proper error. I am not certain that we are getting the proper error back from ibm cloud. Most likely we are just passing back the error messaging from ibmcloud to the user, however I think there needs to be some intercepting on our part to make it more user friendly.
To Reproduce Steps to reproduce the behavior:
Expected behavior It should tell you that your account can only handle one image at a time, unless you upgrade
Screenshots If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
uname -ulimit -adocker -vin Terminal):Additional context Add any other context about the problem here.