Fix missing from docker images? #13675
|
I recently encountered the problem reported and fixed in #12546. To my surprise, when downloading images from docker hub (tags 3.14.0 up to 3.17.0), the fix seems to be missing! Can anyone confirm that I'm not dreaming here? This makes me wonder if anything else is missing... which would be bad... Looking through the project code, it is not clear to me at all how or where the docker images are built and uploaded to docker hub. I hope the image builder just has an out-of-date copy of the |
Replies: 2 comments 3 replies
|
You are not imagining it. The release images and the tagged APISIX source use different copies of the entrypoint script. PR #12546 changed That means adding the fix to an APISIX source tag did not automatically add it to References: the original fix, the fixed 3.17.0 development entrypoint, the release-image entrypoint that is still missing the third cleanup, and the release build copying that separate script. |
|
Tracked by #13752, and fixed by apache/apisix-docker#629 |
You are not imagining it. The release images and the tagged APISIX source use different copies of the entrypoint script.
PR #12546 changed
apache/apisix/docker/debian-dev/docker-entrypoint.sh. The Docker Hub release images are built from the separateapache/apisix-dockerrepository. Its Makefile copiesutils/docker-entrypoint.shinto the Debian or Ubuntu build context, and that copy still removesworker_events.sockbut notstream_worker_events.sock.That means adding the fix to an APISIX source tag did not automatically add it to
apache/apisix:*release images. This is packaging drift, not a stale local Docker cache. The same change needs to be ported toapache/apisix-docker/utils/docker-…