From f32b2a2a98aa86feb4e2fdcc5fd0136684625539 Mon Sep 17 00:00:00 2001 From: Katalina Okano Date: Wed, 7 Oct 2020 18:41:36 -0400 Subject: [PATCH] chore: update dev-container doc --- .devcontainer/devcontainer.json | 1 + README.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json index eae6ec1..cdc8715 100644 --- a/.devcontainer/devcontainer.json +++ b/.devcontainer/devcontainer.json @@ -1,5 +1,6 @@ { "name": "Roleypoly (Bazel, Go, Node)", + // Docker Hub because easier to go fast "image": "roleypoly/dev-container:main", "settings": { "terminal.integrated.shell.linux": "/bin/bash" diff --git a/README.md b/README.md index 70f7e3b..9b59f0f 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ This repo is currently being re-architected into a monorepo, so most processes m This repo can be quickly setup with [VSCode Dev Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) or [GitHub Codespaces](https://github.com/codespaces). This will setup a fully featured Docker container for developing VSCode, including extensions. -If you'd like to not use either of those, a docker image can be built from `.devcontainers/Dockerfile`, or used normally via `docker.pkg.github.com/roleypoly/roleypoly/dev-container`. This use case is not actively investigated, but with tinkering, will work. Feel free to document this process and open a PR :) +If you'd like to not use either of those, it can be imported into your Docker host with `bazel run //src/dev-container`, or pulled from either `roleypoly/dev-container:main` or `docker.pkg.github.com/roleypoly/roleypoly/dev-container:main`. This use case is not actively investigated, but with tinkering, will work. Feel free to document this process and open a PR :) ### Things to Know