Fork of zed-extensions/dockerfile
- Rust 94.7%
- Tree-sitter Query 5.3%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
This PR updates the CI workflow files from the main Zed repository based on the commit zed-industries/zed@3183c04515 The update includes a new version of the extension CLI which adds validation for semantic token rules for languages Co-authored-by: zed-zippy[bot] <234243425+zed-zippy[bot]@users.noreply.github.com> |
||
| .github/workflows | ||
| .zed | ||
| debug_adapter_schemas | ||
| languages/dockerfile | ||
| src | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| extension.toml | ||
| LICENSE | ||
| README.md | ||
Dockerfile Zed Extension
- Tree Sitter: tree-sitter-dockerfile
- Language Server: dockerfile-language-server
Configuration
To support matching filenames other than Dockerfile you can add file_types to your Zed project or user settings:
{
"file_types": {
"Dockerfile": ["Dockerfile.*"]
}
}
Debugging
The extension supports debugging Dockerfile builds with Buildx. The minimal required version of Buildx is v0.28.0. To get Buildx, we recommend installing or updating Docker Desktop. You may alternatively install Buildx manually by following the instructions here.
You can validate your Buildx installation by running BUILDX_EXPERIMENTAL=1 docker buildx dap.
You can create a debug configuration by modifying your project's .zed/debug.json.
{
"label": "Docker: Build", // required, configurable
"adapter": "buildx-dockerfile", // required, must not be modified
"request": "launch", // required, must not be modified
"contextPath": "/home/username/worktree", // optional, defaults to ${ZED_WORKTREE_ROOT}
"dockerfile": "/home/username/worktree/Dockerfile", // optional, defaults to ${ZED_WORKTREE_ROOT}/Dockerfile
"target": "test", // optional, should be a build stage in the Dockerfile
"stopOnEntry": true, // if the debugger should suspend on the first line, defaults to false
"args": [
// additional arguments for the build command
"--build-arg",
"NODE_ENV=development"
]
}
While a build has been suspended, you can evaluate exec to open a shell into the Docker image that has been built up to that point in time.