temporalio / temporalio/samples-server

[Bug] TLS-full sample application fails to run on MAC

Open
#100 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
124
Forks
71
PR merge metrics
No merged PRs in 30d

Description

What are you really trying to do?

run tls-full sample application on MAC laptop.

Understand mTLS setup by using the sample application tls-full

Describe the bug

Sample application exits with below error

ls-full-temporal-1 exited with code 1 | {"level":"fatal","ts":"2025-01-28T12:13:40.909Z","msg":"invalid config: visibility store must be configured","logging-call-at":"/home/runner/work/docker-builds/docker-builds/temporal/common/persistence/visibility/factory.go:96"

Sample application code doesnt run and exits

Minimal Reproduction

Assuming host contains docker and docker-compose rn below commands after checkingout the source code.
cd ./tls/tls-full
./generate-certs.sh
./start-temporal.sh

Environment/Versions
  • OS and processor: [e.g. M1 Mac, x86 Windows, Linux] M1 MAC
  • Temporal Version: [e.g. 1.14.0?] and/or SDK version
  • Are you using Docker or Kubernetes or building Temporal from source? Docker
Additional context

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in tls/tls-full with generate-certs.sh and start-temporal.sh, then reproduce the failure on an M1 Mac using Docker and Docker Compose. Inspect the startup configuration related to the reported visibility-store error. Done means the TLS-full sample starts successfully without the fatal configuration error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, go, shell
Domain
devops, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.