4 ms·
What situation are you in where security vulnerabilities in the Docker image are important to fix, but updating from End-of-Life support for the language isn't?
by rgoulter 7y ago
What situation are you in where security vulnerabilities in the Docker image are important to fix, but updating from End-of-Life support for the language isn't?
(Or even where security of an old Docker image is important, but "has 0 tests" isn't a concern?).
That being said, using a newer underlying Linux image for a Docker image is as copying the Dockerfile and building it, isn't it?
- naranha 7y agoSure all these problems are important to address. But often there is a lack of time/interest to do it. I think the PHP project should simply delete the 5.6 image, since it is insecure and EOL'ed. Then if somebody is interested they can provide an alternative image somewhere...
- vbsteven 7y agoPlainly deleting the image will cause existing setups to break. Something like `cargo yank` would be more appropriate where you can still download the version for existing projects but you cannot use it in new projects anymore. Unfortunately as far as I know docker has no support for anything like that.