Skip to content

Commit

Permalink
[WINDOWS NANOSERVER 1803] Update to Apama Core Community Edition 10.3…
Browse files Browse the repository at this point in the history
….1.1
  • Loading branch information
kpalf committed Apr 28, 2019
1 parent 764f55c commit a206e80
Show file tree
Hide file tree
Showing 4 changed files with 7 additions and 8 deletions.
4 changes: 2 additions & 2 deletions apamacore-nanoserver_amd64/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
# https://hub.docker.com/r/microsoft/nanoserver/

ARG SAG_HOME=C:\\SoftwareAG
ARG ACCE_VERSION=10.3.0.1
ARG ACCE_VERSION=10.3.1.1
ARG ACCE_LIBRARY_VERSION=10.3

#####################################################################
Expand Down Expand Up @@ -39,7 +39,7 @@ LABEL \
arch="x86-64" \
base="microsoft/nanoserver:1803" \
maintainer="Kev Palfreyman (@kpalf)" \
build-date="20181015" \
build-date="20190428" \
version=${ACCE_VERSION}

# Set environment variables inside the image
Expand Down
7 changes: 3 additions & 4 deletions apamacore-nanoserver_amd64/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ You will also see tags for Apama Core on other base images such as CentOS (amd64
The first nanoserver image for this repository was using version 1709, but as new releases become available it's moved forward, for example with version 1803.
The nanoserver 1803 based image for Apama Core can be pulled with the following command:
```
docker pull kpalf/apamacore:10.3.0.1_nanoserver_amd64_1803
docker pull kpalf/apamacore:10.3.1.1_nanoserver_amd64_1803
```

## User ID
Expand All @@ -33,10 +33,9 @@ To find out more about Apama, access full documentation, and download the distri
Windows Server Nano Server has undergone significant changes since first release. The first LTS or GA release is known as `"10.0.14393.<build-number>"` and is around 400MB.
However, the ones we want are the smaller ones that started with the "Fall Creators Update" or "1709", with tags `"1709_KB<knowledge-base-id>"`, and later the "1803" release. The 1709 release started nice and small at 93MB when it was first released, but have grown with each monthly update - the May 2018 is 132MB. The first 1803 release in May 2018 was 115MB, and by October 2018 is 145MB.

To use the nanoserver 1709 image, and layered images such as this one, your host OS needs to be either Windows 10 (Fall Creators Update / 1709), or Windows Server version 1709.
To use the nanoserver 1803 image, and layered images such as this one, your host OS needs to be either Windows 10 (1803), or Windows Server version 1803. The 1803 image might work on a 1709 host but is NOT recommended (I don't test this).
To use the nanoserver 1803 image, and layered images such as this one, your host OS needs to be either Windows 10 (1803 or later), or Windows Server version 1803 or later. The 1803 image might work on a 1709 host but is NOT recommended (I don't test this).

In future we will create a nanoserver 1809 image.
In future we will create a later nanoserver image based on either 1809 (or maybe whatever 19H1 is labelled as).

For more info on Windows Container version compatibility wee the following:
https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility
Expand Down
2 changes: 1 addition & 1 deletion apamacore-nanoserver_amd64/tag.bat
Original file line number Diff line number Diff line change
@@ -1 +1 @@
docker tag apamacore:nanoserver_amd64_1803 kpalf/apamacore:10.3.0.1_nanoserver_amd64_1803
docker tag apamacore:nanoserver_amd64_1803 kpalf/apamacore:10.3.1.1_nanoserver_amd64_1803
2 changes: 1 addition & 1 deletion apamacore-nanoserver_amd64/test-version.bat
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
docker run --rm apamacore:nanoserver_amd64_1803 correlator --version
docker run --rm kpalf/apamacore:10.3.0.1_nanoserver_amd64_1803 correlator --version
docker run --rm kpalf/apamacore:10.3.1.1_nanoserver_amd64_1803 correlator --version

0 comments on commit a206e80

Please sign in to comment.