microsoft / microsoft/vscode-containers
Dockerfile Language Server cannot start right after installing the extension
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 139
- Forks
- 87
- Avg merge
- 9h 15m
- Merged PRs (30d)
- 9
Description
- Install the Container Tools extension.
- Install the Docker DX extension.
- Disable the Container Tools extension.
- Command Palette > Developer: Reload Window
- Open a Dockerfile.
- Enable the Container Tools extension. You will see error toasts popup.
Essentially, this issue only happens if you install Docker DX first and then install Container Tools. If you restart this problem won't happen. From what I can tell it only triggers if you install/enable the Container Tools extension while the Docker DX extension has already been activated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure by installing Docker DX first, then disabling and re-enabling Container Tools after a Developer: Reload Window, with a Dockerfile open. Trace the extension activation and Dockerfile language-server startup path; done means enabling Container Tools no longer produces error toasts and the language server starts without requiring a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100