dcm4che/postgres-dcm4chee same Tag, but different Image Id?

[dirkooms]

Last April I installed an arc-light on a synology. All worked fine.

Now I'm doing the same thing (same docker-compose.yml), but it doesn't work. I noticed that in the db log there were errors that the tables/relations queue_msg and export_task were not present (the old install had 38 tables, the new one only 34 tables).
Then I looked to the images of postgres-dcm4chee. They both have the same Tag '13.1-23', but different Image Id's. The old (good) Image Id is 56c66c402a9e, the new (bad) Image Id is 53b0dd94358d.

I'm a docker newbie, but is it normal that images with the same Tag can have different Image Id's. If not, what is happening here and how can it be resolved?
Any tip will be highly appreciated!

.

[gunterze]

Seems, I accidentally overwrote dcm4che/postgres-dcm4chee:13.1-23 with a version for 5.24.x.
dcm4che/postgres-dcm4chee:13.1-23 should now be restored.

[dirkooms]

Great, seems to be solved. At least I can see the missing tables again. FYI: the Image Id is a new one: 0405b69c7381 (different from both old and new).

Thanks for your quick response. Saved my day (and night).

[gunterze]

Didn't had a backup of old dcm4che/postgres-dcm4chee:13.1-23, so I built a new...