Cassandra based docker compose fails to start

[zoulja]

Expected Behavior

Temporal can be started using docker compose with cassandra, all services must be running

Actual Behavior

Temporal fails to start with the following error:

temporal              | Error: unable to health check "temporal.api.workflowservice.v1.WorkflowService" service: connection error: desc = "transport: Error while dialing: dial tcp 172.18.0.3:7233: connect: connection refused"
temporal              | ('export TEMPORAL_CLI_SHOW_STACKS=1' to see stack traces)
temporal              | Waiting for Temporal server to start...
temporal              | 2024/04/15 12:32:12 error: failed to connect to "[HostInfo hostname=\"172.18.0.2\" connectAddress=\"172.18.0.2\" peer=\"<nil>\" rpc_address=\"0.0.0.0\" broadcast_address=\"172.18.0.2\" preferred_ip=\"<nil>\" connect_addr=\"172.18.0.2\" connect_addr_source=\"connect_address\" port=9042 data_centre=\"datacenter1\" rack=\"rack1\" host_id=\"30e6c360-b68e-4d78-b863-9bb8e4b07646\" version=\"v3.11.9\" state=UP num_tokens=256]" due to error: Keyspace 'temporal_visibility' does not exist

temporal-admin-tools, temporal-ui, temporal-cassandra are Up and running, only temporal itself fails and exits

Steps to Reproduce the Problem

1. Follow the instructions from https://github.com/temporalio/docker-compose?tab=readme-ov-file#how-to-use to clone the repo and get the compose file
2. Start the compose using docker compose -f docker-compose-cass.yml up command
3. Observe the logs and compose services status

Specifications

• Version: the latest one from Git
• Platform: MacOS

[Rodrigo Zhou]

@zoulja Sorry about this, standard visibility support has been removed from docker images, and this docker-compose-cass.yml should've been removed as well. Can you use docker-compose-cass-es.yml instead?