docker hub fails with non-onbuild versions about mod_wsgi-docker HOT 5 CLOSED

The problem is that for some real libmysqlclient-dev was only added to the Python 2.7 images.

Automated builds have been broken on Docker Hub for quite a while, this being the fault of Docker Hub, which is blocking ability to run setcap program even though they recommend using it in their own documentation.

As a result I have been manually building images on Carina Docker system from Rackspace. They are about to shut that down in a few days. I will try and get rebuilt images up. If I can't manage that, not sure how I will be able to update the images as I can't push them from my home network as my Internet speed is too slow.

from mod_wsgi-docker.

Actually, that isn't true. The libmysqlclient-dev library should be in all of them.

from mod_wsgi-docker.

Try again now after pulling latest images.

I may have to try and do it one more time as I suspect I know why it hadn't used correct base image. This is due to a flaw in Carina from Rackspace where if it does the build of an image on different node, it will use base image from Docker Hub rather than what you just built. So will probably need to build base image, push, then build derived image and push. If build base and derived image and then only push, could use older base image. Not more time to try that today though.

from mod_wsgi-docker.

works for me! in the future, could i build and push an image for you?

from mod_wsgi-docker.

I have a new set of images I have been developing which supersede these images. The newer images don't use techniques which Docker recommends in their documentation, yet then bans you from using with automated builds. They will continue to work fine with automated builds.

from mod_wsgi-docker.