Open christilden opened 6 years ago
Just a heads up, it is very hard for me to update images on DockerHub for these images as DockerHub automated builds were broken a couple of years back so that you can't set capabilities on executables. This is why rarely any updates. I don't have upload bandwidth to build at home and push up images. I used to use what free cloud infrastructure out there that I could to do builds and push from them, but they shutdown. It is for that reason, but also that running images as root
is a bad idea that these images have been neglected. Unfortunately I have never blessed for use the replacement I created. I hope to try and resolve what is going to happen by PyCon US this year.
Hi Graham,
Thanks for the information. Unfortunately I am a docker novice, but I am willing to help somehow if I can. A couple thoughts/questions:
Regards, Chris
I can't unfortunately just go and set USER
to be non root
as it will then break things for everyone who relies on the existing behaviour. This is one of the huge problems with Docker images, versioning of them is a pain. For incompatible image changes, it is better to use a different image name. These images weren't originally named though with a version number in the name to use that approach from the outset.
If it comes to it, there is ways for me to update the images on DockerHub, such as go to one of my work offices to upload them (I usually work at home all the time), or create a temporary environment in the cloud where can build them. I could also try and work out how to use one of the CI/CD services out there that allow image building.
I have tested the Python 2.7 variant with an image running a Django application.