Thanks for the feedback, Joel. I haven't heard anything to the contrary from anyone eles, so I've gone ahead and removed the job [1] and updated the README to highlight the presence of the Dockerfile [2]. We can revert the former if necessary down the line. Cheers, Stephen [1] https://review.opendev.org/c/openstack/python-openstackclient/+/947437 [2] https://review.opendev.org/c/openstack/python-openstackclient/+/947440/2 On Wed, 2025-04-16 at 03:02 +0000, Joel McLean wrote:

G'day Stephen,

My experience was that there's many openstack-client clones on dockerhub alone, so I ended up making my own; at the time, I guess I wasn't able to divine that the osclient/python-openstackclient was the official source. Obvious in hindsight, but it was less work to create my own container than it was to sift through looking for the official container (there is no mention of the container on the python-openstackclient/latest documentation page).

Since it's trivial to containerise the python-openstackclient and is very customisable, I could recommend that if you retire the container publication, replace it instead with a documentation of the Dockerfile that could be used to simply stand up one's own container of the client of the appropriate version? Throwing together two paragraphs under a "Running OS Client as a Container" in https://docs.openstack.org/python-openstackclient/latest/ and the Dockerfile/build arguments that was used to build it might go a long way to ensuring anyone who does use it (and who isn't in this list) has a path moving forward.

Kind Regards, Joel

-----Original Message----- From: Stephen Finucane <stephenfin@redhat.com> Sent: Wednesday, 16 April 2025 2:15 AM To: openstack-discuss@lists.openstack.org Subject: [ops][sdk] Does anyone rely on the osclient/python-openstackclient container image?

o/

The python-openstackclient project has an 'osc-upload-image' job that builds and uploads a Docker image to 'osclient/python-openstackclient' on docker.io [1]. This job has been failing intermittently over recent months due to changes in the docker.io rate limits. At this point, I am inclined to remove the job since the image does not appear to be documented anywhere and I'm not aware of anyone relying on it. Before I do though, I'd like to check if this is the case or if someone is in fact relying on it. If anyone *is* doing so, I'd like suggestions for a different image registry we can use, as well as assistance in updating the jobs to use this image registry. If not, I'll likely push to remove this within the next 2-3 weeks.

Cheers, Stephen

[1] https://hub.docker.com/r/osclient/python-openstackclient