devcontainers / devcontainers/cli
Dockerfile for runing devcontainer/cli
- Vorherrschende Sprache
- TypeScript
- Sterne
- 3k
- Forks
- 457
- Ø Merge
- 13 Std. 17 Min.
- Gemergte PRs (30 T.)
- 6
Beschreibung
I think it might be useful to share :
```dockerfile
FROM mcr.microsoft.com/devcontainers/base:0-alpine-3.18
RUN apk add --no-cache \
nodejs \
python3 \
npm \
make \
g++ \
docker-cli \
docker-cli-buildx \
docker-cli-compose \
;
RUN npm i -g @devcontainers/cli
```
And then Build the Dockerfile:
```shell
docker build -t devcontainer-cli .
```
Running the CLI with mounting the Host docker daemon + mounting the workspace :
```shell
docker run -it --rm -v :/workspaces -v /var/run/docker.sock:/var/run/docker.sock devcontainer-cli /bin/ash
```
I Referenced @chrmarti [post](https://github.com/devcontainers/cli/issues/236#issuecomment-1347932178) which was an answer by him regarding some issue.
But i think it's worth to share this Dockerfile ( I Can submit a PR as well ) . of course one can imagine multiple usages and pros:
1. In CI Pipeline where the host of the worker e.g Jenkins will run devcontainer/cli from within this Container based on above image.
2. One that want to test devcontainer/cli without installing things on the machine
Beitragsleitfaden
Rechercherichtung
Start with the proposed Dockerfile and its `docker build` and `docker run` commands, then inspect the repository for existing container or contributor documentation to determine where this belongs. Done means the Dockerfile and usage instructions are included in an appropriate documented location and the described devcontainers CLI workflow is reproducible.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- docker, nodejs, python
- Bereich
- devops, tooling
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 38/100