-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add a Dockerfile to this example repo #112
Comments
Thanks for the request. Can you explain more about what you'd like to do with that Dockerfile? There are a few different contexts I can consider. |
My thought was to create a simple docker container which could be deployed
to container orchestration service.
…On Thu, Dec 26, 2024, 8:44 a.m. Colin Dean ***@***.***> wrote:
Thanks for the request. Can you explain more about what you'd like to do
with that Dockerfile? There are a few different contexts I can consider.
—
Reply to this email directly, view it on GitHub
<#112 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZVKSSTYARUEAEMRGFPZOL2HQW7BAVCNFSM6AAAAABUFB4FP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRSHE2DENZUHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I think what would make sense is Dockerfile producing a container that has just enough Python to simply execute the entrypoint safely. It should follow PythonSpeed's recommendations for Python container best practices. |
I'll look into this next time I have a longer working session on this project. Until then, PRs welcome from you, @Bonythomasv, or any passer-by. |
No description provided.
The text was updated successfully, but these errors were encountered: