From: Duncan P. <du...@ex...> - 2020-11-21 11:15:22
|
Hi Nicholas, With the release of exist 5.0.0 we moved to a new build system, and changed the way we build docker images. It lead to smaller docker images, easier customization, and a tighter integration with the testing and release infrastructure of exist. Due to a bug in the dockerhub code, the new and updated readme is not displayed along the new images. Hence, I put the warning on the old outdated readme, which contains examples in exist v4.x syntax. The updated readme and docker code is in exist’s core repo. The repo containing the old docker stuff has been archived. We cannot delete it yet, as it would break more integrations between docker hub and GitHub, and quickly remove old images we rely on for testing, and which users are depending upon. Other then the fact that the readme displayed on dockerhub is stuck with an outdated version, there are no consequences for users of our docker images whatsoever. Updates continue to be automagical and under the same stable existdb/existdb:TAG address. No code changes are necessary to interact with the docker registry. It will be years before we should consider deleting the old repo, and since very few projects on dockerhub rely on the features that are bugged, a fix anytime soon is very unlikely. If however, the bug is fixed you should immediately see the current readme on dockerhub. If you d like to propose changes to the readme in exist’s core repo or to the warning on the old readme, to make this thing less confusing we would welcome your PR. Greetings Duncan Sent from my iPad > Looking at docker hub, the official image documentation says: > > > This repository will be archived soon. Images will continue to be > available via DockerHub under the old address, but the build will move > to eXist-db's core repo. > > > what are the implications to this decision?? And, why was it made? |