Docker compose file with version errors

Camunda 8 Topics
1

Basically is not possible to perform successfully the docker compose up -d command with the latest docker zip file…
[+] Running 3/7
:heavy_check_mark: Network camundadocker_web-modeler Created 0.0s
:heavy_check_mark: 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.

2

[+] Running 10/13
:heavy_check_mark: Container mailpit Created 0.1s
:heavy_check_mark: Container elasticsearch Created 0.1s
:heavy_check_mark: Container web-modeler-db Created 0.2s
:heavy_check_mark: Container postgres Created 0.2s
:heavy_check_mark: Container web-modeler-websockets Created 0.1s
:heavy_check_mark: Container keycloak Created 0.0s
:heavy_check_mark: Container identity Created 0.0s
:heavy_check_mark: Container zeebe Created 0.0s
⠋ Container optimize Creating 0.1s
:heavy_check_mark: 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

3

Would you please share the Camunda 8 Docker compose link?

4

there it is: Docker Compose | Camunda 8 Docs

5

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

image
image1260×737 94.7 KB

image
image901×578 27.9 KB

6

@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

7

@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.