Why my deploy isn't working well in web modeler localhost?

[stefanie_borges]

How do I configure my zeebe in docker? Do I need to do anything more than this in docker?

WEB MODELER LOCALHOST:
docker compose --profile modeling up -d
Open Web Modeler at localhost:8070

ZEEBE:
docker pull camunda/zeebe
docker run --name zeebe -p 26500-26502:26500-26502 camunda/zeebe:latest

ERROR:

[jonathan.lukas]

Hello @stefanie_borges ,

in order to call zeebe from the web modeler, they both have to be in the same network. Which setup do you use here? The docker compose files provided by us?

Best regards,
Jonathan

[stefanie_borges]

Hi, @ jonathan.lukas!
I didn’t configure any docker compose, when do I configure it? I just installed the images and ran them

[jonathan.lukas]

@stefanie_borges

WEB MODELER LOCALHOST:
docker compose --profile modeling up -d
Open Web Modeler at localhost:8070

This is a docker compose command. So I bet you run web modeler in docker compose.

Which docker compose file do you use here?

[stefanie_borges]

oh, Web Modeler Self-Managed is available to Camunda enterprise customers only? I’m just testing…

[jonathan.lukas]

Hello @stefanie_borges ,

in fact, web modeler can be used like the other components as well.

See here: Licenses | Camunda 8 Docs

However, this would not explain why the deployment does not work.

The question remains which docker compose file you are using here.

Best regards,
Jonathan

[stefanie_borges]

I’m using this camunda/camunda-platform: Links to Camunda Platform 8 resources, releases, and local development config

[jonathan.lukas]

Hi @stefanie_borges ,

while the content around the license is not up-to-date (which is because licensing information is centralised here), the docker compose command you should use is displayed here.

So please remove all containers, networks and volumes from your docker host:

docker system prune -a -f

Now, start the docker compose using this command:

docker compose -f docker-compose.yaml -f docker-compose-web-modeler.yaml up -d

After the startup is complete, the web-modeler application can be accessed and a deployment can be done:

I hope this helps

Jonathan

[stefanie_borges]

hey, @ jonathan.lukas!
Thank you for helping me!!
When I ran this command “docker compose -f docker-compose.yaml -f docker-compose-web-modeler.yaml up -d”
gave this error:
✘ modeler-websockets Error unauthorized: unauthorized to access repository: web-modeler-ee… 3.5s
✘ modeler-webapp Error context canceled 3.5s
✘ modeler-restapi Error context canceled 3.5s
Error response from daemon: unauthorized: unauthorized to access repository: web-modeler-ee/modeler-websockets, action: pull: unauthorized to access repository: web-modeler-ee/modeler-websockets, action: pull

In this case, I am unable to register by running this command:
docker login registry.camunda.cloud
Username: your_username
Password: ******
Error response from daemon: Get “https://registry.camunda.cloud/v2/”: unauthorized

[cpbpm]

I see your indent to setup camunda and web modeler together. But the image you are trying to use is Enterprise image,which is licensed.

Please use this file,camunda-platform/docker-compose/camunda-8.6/docker-compose.yaml at b3f6ad7836b7e913555ae4364d0e3852f18b48e3 · camunda/camunda-platform · GitHub to setup web-modeler and camunda zeebe,

The same file is one level inside the github tree.

[jonathan.lukas]

Good catch @cpbpm !

The docker-compose is almost the same, but the images come from the public docker hub and are licensed just like the other components.

[stefanie_borges]

Hey, @cpbpm!!
Thanks for help!! Now its all working well!!

[stefanie_borges]

Hi! @jonathan.lukas!!
Thanks to u too!!