-
Notifications
You must be signed in to change notification settings - Fork 81
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
Update Python image on Dockerhub #341
Comments
Hi @ralienpp, thanks for the question. Does your build rely on the OpenSSL 1.1.1 fork or the OpenSSL 3 provider? |
We rely on the OpenSSL 3 provider. |
Good to know there is some interest in this. Would you be interested contributing your build as an updated Dockerfile, e.g./i.e., here? But of course, we could also add it as another demo... |
I think there's nothing wrong with what you already have. My wish is to update the image on Dockerhub, using the recipe you already have, but with a new version of Our Dockerfile doesn't use Alpine, but Ubuntu; and it is much simpler:
|
If you're referring to https://github.com/open-quantum-safe/liboqs-python/blob/main/docker/Dockerfile (?) there is something wrong imo (outdated, rather): It's not based on |
Since this issue falls outside the scope of oqs-demos and relates to liboqs-python, do you think we should close it, @baentsch? |
Well, it is a report of a real shortcoming and it shouldn't matter where it's located. If we'd want to update it to On the other hand, @ralienpp seems to be the only user of the image and didn't respond to the question as to whether he may be willing to contribute his Dockerfile to ease our effort, nor whether we're really talking about the same thing. |
I agree with your point. Let’s proceed with what you suggested. |
I use OQS in a project with Python and I was wondering whether the image could be updated (the page says it is discontinued, but encourages visitors to raise this point here).
Right now we have a CI pipeline that builds it in accordance with our needs, but it would simplify matters if we could use an image provided by the development team.
The text was updated successfully, but these errors were encountered: