Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug] DevContainer doesn't start the temporal server image #282

Open
ross-p-smith opened this issue Jun 8, 2023 · 3 comments · May be fixed by #283
Open

[Bug] DevContainer doesn't start the temporal server image #282

ross-p-smith opened this issue Jun 8, 2023 · 3 comments · May be fixed by #283
Labels
bug Something isn't working

Comments

@ross-p-smith
Copy link

ross-p-smith commented Jun 8, 2023 •
edited by sync-by-unito bot
Loading

When you open this repo in vscode you can optionally chose to run it in a devcontainer - which is fantastic! However all the images start apart from the auto-setup:latest container which I assume is the Temporal Server.

image

When I look in the logs of the failing container it mentions a missing file which I can confirm is not in the repo

config/dynamicconfig/development_es.yaml: no such file or directory

Temporal CLI address: 172.18.0.3:7233.
+ + grep -q temporal SERVING
operator cluster health
2023/06/08 16:12:22 Loading config; env=docker,zone=,configDir=config
2023/06/08 16:12:22 Loading config files=[config/docker.yaml]
{"level":"info","ts":"2023-06-08T16:12:22.452Z","msg":"Build info.","git-time":"2023-05-15T23:50:55.000Z","git-revision":"45d22540323e59e4cd3fd62139b73409f1264fb3","git-modified":true,"go-arch":"amd64","go-os":"linux","go-version":"go1.20.4","cgo-enabled":false,"server-version":"1.20.3","debug-mode":false,"logging-call-at":"main.go:143"}
Unable to create dynamic config client. Error: unable to validate dynamic config: dynamic config: config/dynamicconfig/development_es.yaml: stat config/dynamicconfig/development_es.yaml: no such file or directory

Minimal Reproduction

Open in Remote Containers and see if the Temporal Service is running.

Environment/Versions

  • OS and processor: Windows running WSL and the DevContainer
  • Latest from main
@ross-p-smith ross-p-smith added the bug Something isn't working label Jun 8, 2023
@ross-p-smith
Copy link
Author

Digging deeper - this looks the same as temporalio/temporal#2755 - if the Temporal Service doesn't work in docker-compose, then I cant understand why it is defined in the /.devcontainer/docker-compose.yml

@ross-p-smith ross-p-smith linked a pull request Jun 8, 2023 that will close this issue
Open
@sbocinec
Copy link

@ross-p-smith I guess you already found a solution, only for future reference - I think the issue was not caused by the docker-compose, but the fact Temporal has removed the development_es.yaml file from v1.17 forward https://github.com/temporalio/temporal/tree/v1.17.6/config/dynamicconfig

The error actually correctly reports the file is not found:
Unable to create dynamic config client. Error: unable to validate dynamic config: dynamic config: config/dynamicconfig/development_es.yaml: stat config/dynamicconfig/development_es.yaml: no such file or directory

The solution is to either change the DYNAMIC_CONFIG_FILE_PATH var or not set the var at all.

@kishoreh3bist
Copy link

kishoreh3bist commented Sep 6, 2024 •
edited
Loading

I was able to resolve this issue with a hack. I copied the dynamicconfig to the folder from where I was running the docker-compose up -d command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Temporal running locally in a DevContainer ross-p-smith/samples-go
3 participants
@sbocinec @ross-p-smith @kishoreh3bist