Expected Behavior
Temporal is accessible on http://localhost:7233 when using dev setup described in https://github.com/temporalio/samples-server/blob/7c22fa05a6f4c25358ac4623d671f5573ecdf857/compose/docker-compose-dev.yml
Actual Behavior
Cannot reach the server. Using the Go-SDK i keep getting "failed reaching server: context deadline exceeded". Using the temporal CLI, it hangs when trying to reach the server.
Note that the UI is available and accessible at localhost:8233.
Steps to Reproduce the Problem
- Copy the contents of https://github.com/temporalio/samples-server/blob/7c22fa05a6f4c25358ac4623d671f5573ecdf857/compose/docker-compose-dev.yml to a local file. Let's call it
docker-compose.dev.yml
- Start the service using
docker compose -f docker-compose.dev.yml up -d
- Run the following command:
docker run --rm temporalio/admin-tools:1.28.3 \
temporal operator namespace describe default \
--address localhost:7233
My suspicion is that this is an issue with docker, since the issue started to appear after doing a system upgrade.
Specifications
- Version:
- temporalio/temporal: 1.6.2
- temporalio/admin-tools: 1.28.3
- Go-SDK: 1.36.0
- Platform: Arch/linux amd64
Expected Behavior
Temporal is accessible on http://localhost:7233 when using dev setup described in https://github.com/temporalio/samples-server/blob/7c22fa05a6f4c25358ac4623d671f5573ecdf857/compose/docker-compose-dev.yml
Actual Behavior
Cannot reach the server. Using the Go-SDK i keep getting "failed reaching server: context deadline exceeded". Using the temporal CLI, it hangs when trying to reach the server.
Note that the UI is available and accessible at localhost:8233.
Steps to Reproduce the Problem
docker-compose.dev.ymldocker compose -f docker-compose.dev.yml up -ddocker run --rm temporalio/admin-tools:1.28.3 \ temporal operator namespace describe default \ --address localhost:7233My suspicion is that this is an issue with docker, since the issue started to appear after doing a system upgrade.
Specifications