Docker compose file with version errors

[Rafael_Oliveira]

Basically is not possible to perform successfully the docker compose up -d command with the latest docker zip file…
[+] Running 3/7
Network camundadocker_web-modeler Created 0.0s
Network camundadocker_camunda-platform Created 0.0s
⠋ Container mailpit Creating 0.0s
⠋ Container postgres Creatin… 0.0s
⠋ Container web-modeler-websockets Creating 0.0s
✘ Container web-modeler-db E… 0.0s
⠋ Container elasticsearch Cr… 0.0s
Error response from daemon: No such image: postgres:14.5-alpine

I fixed the postgres container manually however the others containers are with errors too.

[Rafael_Oliveira]

[+] Running 10/13
Container mailpit Created 0.1s
Container elasticsearch Created 0.1s
Container web-modeler-db Created 0.2s
Container postgres Created 0.2s
Container web-modeler-websockets Created 0.1s
Container keycloak Created 0.0s
Container identity Created 0.0s
Container zeebe Created 0.0s
⠋ Container optimize Creating 0.1s
Container web-modeler-restapi Cr… 0.0s
✘ Container operate Error response… 0.0s
⠋ Container tasklist Creating 0.0s
⠋ Container web-modeler-webapp Cre… 0.0s
Error response from daemon: No such image: camunda/operate:8.7.8

[cpbpm]

Would you please share the Camunda 8 Docker compose link?

[Rafael_Oliveira]

there it is: Docker Compose | Camunda 8 Docs

[cpbpm]

I did not see any issues, All the containers are running as expected. I used Podman/Portainer to test the images:

[nathan.loding]

@Rafael_Oliveira - I was able to start this configuration as well without error. The error’s you see (“No such image” for camunda/operate:8.7.8 and postgresL14.5-alpine) are strange - is Docker running through a proxy or a cache or a private hub perhaps? camunda/operate:8.7.8 definitely exists:

https://hub.docker.com/layers/camunda/operate/8.7.8/images/sha256-a89b5bf8408557f325e7e95c7ac81372f0963703138d0dd6e20a94af6a2015e2

[Rafael_Oliveira]

@nathan.loding @cpbpm I executed the Docker Compose again without making any changes, and it started working properly. However, there’s no explanation for what occurred.