-
|
I've created multi-arch builds over at https://hub.docker.com/r/mrnr91/uvicorn-gunicorn-fastapi However I'd rather have them over here of course :) Is there a particular reason that you don't have multi arch builds? (Note - python-slim wasnt buildable probably because pip had to build packages from source) |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
@mnorrsken do you have the source code? I assume this is a bit more involved than changing |
Beta Was this translation helpful? Give feedback.
-
|
Not really. Its just that you have to build the dependency images with multi arch too. Tbh I moved on from this and now I just use a standard python image with fastapi and uvicorn in requirements. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! Now that Uvicorn supports managing workers with Because of that, I deprecated this Docker image: https://github.com/tiangolo/uvicorn-gunicorn-docker#-warning-you-probably-dont-need-this-docker-image And by using an official Python base image you would get multi-arch by default. 😎 |
Beta Was this translation helpful? Give feedback.
Thank you!
Now that Uvicorn supports managing workers with
--workers, including restarting dead ones, there's no need for Gunicorn. That also means that it's much simpler to build a Docker image from scratch now, I updated the docs to explain it.Because of that, I deprecated this Docker image: https://github.com/tiangolo/uvicorn-gunicorn-docker#-warning-you-probably-dont-need-this-docker-image
And by using an official Python base image you would get multi-arch by default. 😎