New v5 and new roadmap

[mistraloz]

New v5 and new roadmap

[MrMage]

@mistraloz Thank you for all the work that went into these images; I've been using them for years. I do wonder whether it would make sense to release a "small" v5 upgrade that only upgrades the Ubuntu version to 22.04, with the remaining changes being pushed out to v6 and beyond? That could already let users benefit from overall system performance improvements affecting PHP while hopefully incurring less work than making the other breaking changes.

[robjuz]

@mistraloz
First of all thanks for the great work done so far. I'm using this images in my daily work in dev and prod. I just love how this images are easy to use and overcome all the pitfalls that come when working with docker.

I would love to support your work with v5. Just let me know how can I help!

[nguyenk]

Hello @robjuz We are truely very happy to read this message. @mistraloz is currently off, he weill be back in 3 weeks. I'm sure he will get back to you when he returns.

In any case, any help will be greatly appréciated.

[robjuz]

My first idea would be to migrate from ubuntu to the official php images based on debian and alpine. There is also a apache version. This would speedup the delivery and reduce the image size.

I'm waiting for your feedback.

[mistraloz]

Hello @robjuz sorry for the delay of my answer. You can follow the progress of the v5 dev onto https://github.com/thecodingmachine/docker-images-php/blob/v5/ROADMAP_v5.md
Currently it's still not possibilible to contribute with PR because i make lof be refactor about structure of the files on the branch then i will hard reset and link the changes... BUT if you have any suggestion or advices please tell me here.

I hope to open the v5 to contribution on 2th october. After that we can split the work on the different features. We can also have a visio meeting with anyone wants to contribute (sometime it's easy to challenge the global vision or to improve the motivation).

[benjilebon]

Concerning the alpine image, i've seen discussions going around concerning the speed and raw performance around execution in alpine based environments, this thread demonstrates an example using python : https://superuser.com/questions/1219609/why-is-the-alpine-docker-image-over-50-slower-than-the-ubuntu-image

While this isn't talking specifically about php, it actually affects it in some way ( TL;DR: Alpine is using a different C base library implementation called "musl", which has some differences in implementing memory allocation compared to glibc, used in debian based distros)

I agree to the idea of having a big reduced time on delivery & image size, but potentially losing about ~50% of performance on a production environment is not acceptable, maybe keeping a sort-of long term support for debian based image would be beneficial for performance-sensible projects if that kind of problem shows-up in alpine versions

(just a heads-up for now, but i'm okay to contribute in some way with benchmarks if needed in the future)

[robjuz]

Debian-slim is really small. I was a big fan of alpine, but get into some issues with python libraries and switched to debian-slim. Best move ever.