-
Notifications
You must be signed in to change notification settings - Fork 197
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.
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
[Bug] DevContainer doesn't start the temporal server image #282
Comments
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 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 The error actually correctly reports the file is not found: The solution is to either change the |
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. |
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.
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
Minimal Reproduction
Open in Remote Containers and see if the Temporal Service is running.
Environment/Versions
The text was updated successfully, but these errors were encountered: