-
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
v5 base Image #2
Comments
I don't really know to be very honest! We can try and find out. 👍 from me on attempting to switch to a multistage build and just copying the necessary binaries over though. |
yeah I'm looking at this approach: I'd love to get the final running image under 1GB 😆 |
i'm messing with it right now and if it works, i'll put. a PR in for a v5 folder/dockerfile |
also these are interesting: https://github.com/OSGeo/gdal/tree/master/gdal/docker do you know how much/which parts of GDAL/GEOS/etc RP uses? |
Those look potentially helpful!
I don't, sorry. my gut says just go with whatever is needed for Django (don't try to pare it down too much)... Semi-related, I soured on Alpine after discovering the https://www.caktusgroup.com/blog/2017/03/14/production-ready-dockerfile-your-python-django-app/ |
I like that approach @tobiasmcnulty. What I'm testing now is a combo of that- do the deps/pip installs in a builder stage then just |
@tybritten how's v5 + docker working for you ? I've not looked much at these docker builds since v5 was released. |
not much is different from v4. Images sizes are still bigger than I'd like (over 1.1GB even with using the multistage builds) i really can't seem to figure out exactly how much of those GEOS libs etc are needed so i think we can stick with the v4 base for now. |
Since we're already upgraded to 5.x, I'm looking at revving the docker images we're testing with as well. The go service ones (MR, Courier, Indexer, Archiver) are pretty slim to begin with but the main RP one is still big. I'd like to switch to a multistage build, hopefully for both the base as well as the main rapidpro image.
@smn I don't know much about these geos libs- can we build them and then transfer them to a final image or do we need all the prereqs?
The text was updated successfully, but these errors were encountered: