Closed RyuSA closed 2 years ago
Quick workaround: use a semantic version tag. current latest version is 0.205.5
https://github.com/microsoft/vscode-dev-containers/blob/main/containers/java/history/0.205.5.md
$ docker run --rm -it mcr.microsoft.com/vscode/devcontainers/java:0.205.5-17 java -version
openjdk version "17.0.4" 2022-07-19 LTS
OpenJDK Runtime Environment Microsoft-38107 (build 17.0.4+8-LTS)
OpenJDK 64-Bit Server VM Microsoft-38107 (build 17.0.4+8-LTS, mixed mode, sharing)
I think this issue is tracked on devcontainers/images#102
oh, I didn't know the issue thanks.
the change will be synced to this repo too?
the change will be synced to this repo too?
The source repository for that image has recently been changed from here to there. Please see #1589.
Thanks a lot @eitsupi ! š Let me close the issue.
$ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.4 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.4 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal
$ arch x86_64
I didn't notifythe bug since I used local image cache long time for my devcontainer environment. But when I tried to rebuild the container image without cache, I got a build error today which said "hey, this container does not have java 17 but java 11".
I think the images must contain Java 17 to set up for Java 17 development environment. Isn't it expected behavier?
Thank you,