Why did Laradock (docker-compose) install functionally identical(??not sure??) images?

Question

Docker

My Laradock (docker-compose) bucked hard yesterday, cured only by deleting all images from the system, and then, after launch

docker-compose up -d nginx mysql phpmyadmin

, new ones were installed. But I don’t understand if it’s normal that in those places that were just problematic (initially it was impossible to log in to MySQL through phpMyAdmin), functionally identical outwardly images were installed (highlighted in bold):

Comp @ me: ~ $ docker images
REPOSITORY the TAG ID the IMAGE CREATED the SIZE
laradock_nginx latest 7503362ab5cf ago 27.6MB 9 minutes
laradock_php-fpm latest 7726cbc0043f ago 828MB 10 minutes
laradock_workspace latest 91b1c8d7b9b3 ago 1.16GB 39 minutes
laradock_phpmyadmin latest 0afaaec4b774 About an hour ago 474MB
laradock_mysql latest f3e20ed0962d About an hour ago 514MB
laradock/php-fpm latest-7.4 3d09282b0597 37 hours ago 488MB
laradock/workspace latest-7.4 31867821fd5c 38 hours
ago 798MB
mysql 8.0 5a4e492065c7 12 days ago 514MB
docker 19.03-dind fa3b7a5678ec 5 weeks ago 236MB
phpmyadmin/phpmyadmin latest 2e5141bbcbfb 2 months ago 474MB

This is fine? Or is this a continuation of the original glitch?

Should something be done about this? In principle, it works fine again, but I want to understand for the future, without becoming a docker guru through reading thick documentation :)

Thank you.