You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+28-26Lines changed: 28 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,7 @@ A packer + ansible project to build Docker images for use by the various THREDDS
4
4
The Docker images are used as the basis for Jenkins build nodes as well as a custom GitHub action for testing the various THREDDS projects.
5
5
The image is based off the latest available image for `ubuntu 24.04`.
6
6
The docker images produced by packer are called "thredds-test-environment" (for use by Jenkins) of `thredds-test-action` (for use by the GitHub action).
7
+
The image used by Jenkins is hosted on the Docker Hub Container Registry, while the image used by the GitHub action is hosted on the GitHub Container Registry.
7
8
8
9
## Requirementsco
9
10
@@ -13,6 +14,7 @@ The docker images produced by packer are called "thredds-test-environment" (for
13
14
If this is your first time running the build, you will need to initialize packer using:
`<type>` will one or more (separated by commas) of the following:
39
-
*`docker.docker-jenkins`: Provision a Docker container and generate and tag a local Docker image (`docker.unidata.ucar.edu/thredds-test-environment:20.04`).
41
+
*`docker.docker-jenkins`: Provision a Docker container and generate and tag a local Docker image (`docker.io/unidata/thredds-test-environment:20.04`).
40
42
*`docker.docker-github-action`: Provision a Docker container for use with GitHub Actions and tag a local docker image (`ghcr.io/unidata/thredds-test-action:v3`).
41
43
*`docker.docker-export`: Provision a Docker container and generate a local Docker image as a file (`image.tar`).
42
44
@@ -52,18 +54,18 @@ Packer will run the builders in parallel, so the total time to create the `thred
52
54
If using `docker-jenkins`, then once the image is built you can test out the environment by using:
53
55
54
56
~~~bash
55
-
docker run -i -t --rm docker.unidata.ucar.edu/thredds-test-environment:24.04
57
+
docker run -i -t --rm docker.io/unidata/thredds-test-environment:24.04
56
58
~~~
57
59
58
60
These images are built using the multiplatform feature of Docker, and only `linux/amd64` images are produced.
59
61
If you are on a `arm64` based mac, you will need to run:
60
62
61
63
~~~bash
62
-
DOCKER_DEFAULT_PLATFORM=linux/amd64 docker run -i -t --rm docker.unidata.ucar.edu/thredds-test-environment:24.04
64
+
DOCKER_DEFAULT_PLATFORM=linux/amd64 docker run -i -t --rm docker.io/unidata/thredds-test-environment:24.04
63
65
~~~
64
66
65
67
Note that images are not pushed as part of this build process.
66
-
Pushes can be done via the normal docker mechanisms, e.g. `docker image push docker.unidata.ucar.edu/thredds-test-environment:24.04` and `docker image push ghcr.io/unidata/thredds-test-action:v3`.
68
+
Pushes can be done via the normal docker mechanisms, e.g. `docker image push docker.io/unidata/thredds-test-environment:24.04` and `docker image push ghcr.io/unidata/thredds-test-action:v3`.
67
69
68
70
## Project layout
69
71
@@ -117,7 +119,7 @@ We use the following roles when provisioning our images:
117
119
118
120
### maven:
119
121
* location: `/usr/thredds-test-environment/mvn`
120
-
* version: `3.9.11`
122
+
* version: `3.9.12`
121
123
122
124
### Java:
123
125
* Temurin (latest version available from adoptium.net)
@@ -158,26 +160,26 @@ We use the following roles when provisioning our images:
0 commit comments