docker pull rabbitmq:3.13 is giving a manifest unknown error

[gregsmith-vasion]

There was a push to Docker Hub at Dec 13, 2024 at 11:52 pm (US Eastern)...

docker pull rabbitmq:3.13                           
3.13: Pulling from library/rabbitmq
manifest for rabbitmq:3.13 not found: manifest unknown: manifest unknown

Any ideas what's going on here? Pulling rabbitmq:4 and even rabbitmq:3.13.6 works fine.

[mkniazuk123]

docker pull rabbitmq:3 also does not work

[vicolby]

rabbitmq:3-management not found also

[gregsmith-vasion]

I have a feeling 3.13.7 was recently introduced and something went wrong.

Docker tags 3 and 3.13 were likely updated to point to the latest broken build.

Workaround for now is to lock to 3.13.6 tags.

[knutster]

Same here, had to revert to 3.13.6. Will teach me not to use ranges.

[dimadeush]

4.0.4 it seems working now, the same with 3.13.6. The issue is in 3.13.7 version.

[Enteee]

same issue for docker pull rabbitmq:3.13.7-management-alpine
did use this image fore quite some time now, but it stopped working yesterday.

[JuanxCursed]

+1 same issue here

[rockit666]

Help please

[michaelklishin]

@tianon @yosifkit this cloud have something to do with the OS bump for both Alpine 0584c9d and Ubuntu 24.04 (specifically for 3.13.x) #746 recently. Or just an infrastructure issue of sorts, because image updates usually do not affect older tags.

Do you folks know what may be going on?

[michaelklishin]

I have a feeling 3.13.7 was recently introduced and something went wrong

3.13.7 is from late August 2024.

While I won't pretend I know what may be going on but something that did happen recently was a new image build after the two OS updates mentioned above.

3.13.7 is the only affected tag according to a quick docker pull test on two different hosts. 4.0.4 is perfectly fine.

For many environments, this may be a good moment to move to 4.x, the only community supported series.

[michaelklishin]

I don't think we need any more +1s or questions as to what may be going on. Now we have to wait for the maintainers and/or Docker Hub infrastructure folks find what's going on and rebuild, republish 3.13.7. That won't happy any sooner if a few more speculative comments or +1s were posted.

We did establish that only the 3.13.7 tag is affected. 4.0.4 or 3.13.6 are fine. Switching to 4.0.4 where possible is what I'd recommend.

[michaelklishin]

We have an update from a Docker, Inc team.

The issue is not entirely specific to this image. Please see [1][2].

There is an ongoing technical operations call, so the issue is not being ignored, quite the contrary.

1. https://www.dockerstatus.com/
2. Manifest for docker:latest not found: manifest unknown docker#519

[LaurentGoderre]

Closing in favor of the issue mentioned above.

[michaelklishin]

docker pull rabbitmq:3

docker pull rabbitmq:3.13.7

both work for me now.