I found out that official django container is deprecated. Why you don't want to support it?
For most usages of this image, it was already not bringing indjango
from this image, but actually from your project'srequirements.txt
, so the only "value" being added here was the pre-installing ofmysql-client
,postgresql-client
, andsqlite3
for various uses of thedjango
framework.
I think the point we are trying to make is that it’s fundamentally not a good thing to try and distribute a one-size fits all docker image for a specific framework.
For reference here is one you can use yourself:
FROM python:3
COPY requirements.txt .
RUN pip install -r requirements.txt
COPY . .
CMD [ "gunicorn", "my.app" ]
If someone is unable to make an equivalent Dockerfile then they will be really confused when they realise that they need to customise it, because few projects are as simple as that.
You should also likely not embed Apache inside your app container - it’s kind of missing the general idea of Docker.
To re-iterate: The Django project had no hand in creating the ‘official’ image. The Docker project retired the original Django image for reasons that are clearly explained here, and those reasons still hold today.
Tom
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f07ad32e-e74f-4cd3-945a-ed92692c2209%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFNZOJP5k%3Dsn8VkdwseuVqnMC6X40y349urNMRFZfD7FEypvbg%40mail.gmail.com.