linkerd2/.devcontainer
dependabot[bot] e5830ad05b
build(deps): bump linkerd/dev from 39 to 40 (#10825)
* build(deps): bump linkerd/dev from 39 to 40

Bumps [linkerd/dev](https://github.com/linkerd/dev) from 39 to 40.
- [Release notes](https://github.com/linkerd/dev/releases)
- [Commits](https://github.com/linkerd/dev/compare/v39...v40)

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Alex Leong <alex@buoyant.io>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Alex Leong <alex@buoyant.io>
2023-05-09 10:57:19 -07:00
..
README.md dev: Move devcontainer tooling to dedicated repo (#9198) 2022-08-24 11:01:49 -07:00
devcontainer.json build(deps): bump linkerd/dev from 39 to 40 (#10825) 2023-05-09 10:57:19 -07:00

README.md

devcontainer

This directory provides a devcontainer configuration that configures a reproducible development environment for this project.

The devcontainer configuration is maintained in the linkerd/dev repository.

Docker

This configuration currently uses the parent host's Docker daemon (rather than running a separate docker daemon within in the container). It creates devcontainers on the host network so it's easy to use k3d clusters hosted in the parent host's docker daemon.

Customizing

This configuration is supposed to provide a minimal setup without catering to any one developer's personal tastes. Devcontainers can be extended with per-user configuration.

To add your own extensions to the devcontainer, configure default extensions in your VS Code settings:

    "remote.containers.defaultExtensions": [
        "eamodio.gitlens",
        "GitHub.copilot",
        "GitHub.vscode-pull-request-github",
        "mutantdino.resourcemonitor",
        "stateful.edge"
    ],

Furthermore, you can configure a dotfiles repository to perform customizations with a configuration like:

    "dotfiles.repository": "https://github.com/olix0r/dotfiles.git",