Not maintaining anymore as VSCode has a number of native containers now
A docker container to auto spin up:
Tool | Default Version (if blank) | Custom Version Support | Custom Version Example | Notes |
---|---|---|---|---|
Git | Latest from apt | No | N/A | |
Azure CLI | Latest from apt | Yes | 2.2.0 | |
AWS CLI | Latest from AWS site | No (Possible?) | N/A | Using v2.x. For v1.x, need to edit dockerfile per instructions there |
GCP CLI | Latest from apt | Yes | 284.0.0 | |
Azure Python SDK | Latest from pip | TBD | 4.0.0 | |
Helm | Latest from helm site | Yes | 3.1.2 | |
Terraform | 0.12.24 | Yes (Required) | 0.12.23 | |
Kubectl | Latest from apt | Yes | 1.17.4 | |
Az Functions Tools | Latest from apt | Yes | 3.0.2245 |
(Also installs all dependencies)
Specify a version number of 0 to not install that tool
Cloud | Status |
---|---|
Azure | Done |
GCP | TODO |
AWS | TODO |
Sets user.name and user.email. Credentials are pulled from the VS Code credential helper, otherwise will need to handle credentials once in the container
Set environment variabes by populating .env.sample and renaming to .env If using VS Code to develop in a container, will also need the .env in the root of the code folder
- Run the command Remote-Containers: Add Development Container Configuration Files
- Edit devcontainer.json and change "dockerComposeFile": "docker-compose.yml" to "dockerComposeFile": "". Also comment out remoteuser: vscode
- Run command: Remote-Containers: Reopen in Container