From 69b8ac7a1802d4af02a6062c2b58dab8fc691dfc Mon Sep 17 00:00:00 2001 From: deviantony Date: Fri, 4 Nov 2022 08:10:25 +0000 Subject: [PATCH] bump version in files --- Makefile | 4 ++-- README.md | 8 ++++---- examples/python-extension/Dockerfile | 2 +- examples/zsh/Dockerfile | 2 +- user-toolkits/alapenna/Dockerfile | 2 +- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/Makefile b/Makefile index 146c810..6eaf5a4 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ -# Note: these can be overriden on the command line e.g. `make VERSION=2022.10` -VERSION=2022.10 +# Note: these can be overriden on the command line e.g. `make VERSION=2022.11` +VERSION=2022.11 .PHONY: setup clean base alapenna diff --git a/README.md b/README.md index 2ebf46a..192c8d1 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ docker run -it --init \ -p 3000:3000 -p 9000:9000 -p 9443:9443 -p 8000:8000 \ -v /var/run/docker.sock:/var/run/docker.sock \ --name portainer-devkit \ - portainer/dev-toolkit:2022.10 + portainer/dev-toolkit:2022.11 ``` Now you can access VScode directly at http://localhost:3000 and start coding (almost)! @@ -38,7 +38,7 @@ The Docker image is based on the OpenVSCode image provided by Gitpod: https://gi The `portainer/dev-toolkit` **Linux AMD64** image is using DockerHub automatic builds to build images based on this git repository tags. -E.g. creating a new `2022.10` tag in this repository would automatically build `portainer/dev-toolkit:2022.10`. +E.g. creating a new `2022.11` tag in this repository would automatically build `portainer/dev-toolkit:2022.11`. # Manual build @@ -69,7 +69,7 @@ docker run -it --init \ -p 3000:3000 -p 9000:9000 -p 9443:9443 -p 8000:8000 \ -v /var/run/docker.sock:/var/run/docker.sock \ --name portainer-devkit \ - portainer/dev-toolkit:2022.10 + portainer/dev-toolkit:2022.11 ``` Now you can access VScode directly at http://localhost:3000 and start coding (almost)! @@ -86,7 +86,7 @@ All you will need is to build it first: docker buildx build -t my-devkit -f examples/zsh/Dockerfile . ``` -Then you can use the instructions above to run it, just replace the official `portainer/dev-toolkit:2022.10` with your image: +Then you can use the instructions above to run it, just replace the official `portainer/dev-toolkit:2022.11` with your image: ``` docker run -it --init \ diff --git a/examples/python-extension/Dockerfile b/examples/python-extension/Dockerfile index ed9f7a8..c496cda 100644 --- a/examples/python-extension/Dockerfile +++ b/examples/python-extension/Dockerfile @@ -1,4 +1,4 @@ -FROM portainer/dev-toolkit:2022.10 +FROM portainer/dev-toolkit:2022.11 # First, you'll need to retrieve the unique identifier associated to the extension # It can be found on VSCode extension marketplace: https://marketplace.visualstudio.com/items?itemName=ms-python.python diff --git a/examples/zsh/Dockerfile b/examples/zsh/Dockerfile index 369c018..1b479e8 100644 --- a/examples/zsh/Dockerfile +++ b/examples/zsh/Dockerfile @@ -1,4 +1,4 @@ -FROM portainer/dev-toolkit:2022.10 +FROM portainer/dev-toolkit:2022.11 ENV HOME /root diff --git a/user-toolkits/alapenna/Dockerfile b/user-toolkits/alapenna/Dockerfile index c28797f..0ae7285 100644 --- a/user-toolkits/alapenna/Dockerfile +++ b/user-toolkits/alapenna/Dockerfile @@ -1,4 +1,4 @@ -FROM portainer/dev-toolkit:2022.10 +FROM portainer/dev-toolkit:2022.11 # This image uses /root as the home instead of /home/workspace ENV HOME /root