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
+32-18Lines changed: 32 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,16 @@ If your computer is behind a network proxy, this may cause issues related to usi
49
49
Though ANMS can be run behind a proxy; building the ANMS Docker images from behind a network proxy may result in errors.
50
50
51
51
The first steps in each of the container image `Dockerfile` is to attempt to download an APLNIS root CA to validate the APLNIS HTTPS proxy.
52
-
When building images outside of the APLNIS, this download will gracefully fail and the image will not be able to run within the APLNIS.
52
+
When building images outside of the APLNIS, this download will gracefully fail and the image will not be able to run within the APLNIS. The URL for this certificate can be changed for users requiring equivalent functionality on their own networks.
53
+
54
+
### Special Notes on Podman
55
+
56
+
If not otherwise specified, most commands in this document allow podman and docker to be used interchangeably. It is also possible to install an alias (provided in most package managers) to map `docker` to `podman` if desired.
57
+
58
+
Podman, running as a standard user, is typically unable to bind to **low-numbered ports**. It is recommended to edit the `.env` file and uncomment the lines at top for AUTHNZ_PORT and AUTHNZ_HTTPS_PORT to remap those services to a higher port number. In the directions below, you would then use for example http://localhost:8084 and https://localhost:8443 instead of the default.
59
+
60
+
Note: If running on a system where **SELinux** is enabled, the system will not start if the appropriate security groups have not been defined. As an alternative, the `security_opt` sections can be commented out in the *-compose.yml files if required.
61
+
53
62
54
63
### Upgrading ANMS
55
64
@@ -63,29 +72,35 @@ The following command sequence uses standard Docker commands to stop all contain
The current ANMS capability is designed to run on `localhost` and on a development virtual machine.
69
-
This guide presumes that you can either connect via a VMRC remote console or with ssh tunnelling to the machine, hence the use of `localhost` in db connection information and in URLs.
70
-
If you deploy this to a VM, you will need to replace `localhost` with the hostname of the machine where it is deployed.
71
-
72
-
### Special Notes on Podman
76
+
## ANMS build and deploy
73
77
74
-
If not otherwise specified, most commands in this document allow podman and docker to be used interchangeably. It is also possible to install an alias (provided in most package managers) to map `docker` to `podman` if desired.
78
+
## Quickstart
75
79
76
-
Podman, running as a standard user, is typically unable to bind to **low-numbered ports**. It is recommended to edit the `.env` file and uncomment the lines at top for AUTHNZ_PORT and AUTHNZ_HTTPS_PORT to remap those services to a higher port number. In the directions below, you would then use for example http://localhost:8084 and https://localhost:8443 instead of the default.
80
+
`./quickstart.sh`
77
81
78
-
Note: If running on a system where **SELinux** is enabled, the system will not start if the appropriate security groups have not been defined. As an alternative, the `security_opt` sections can be commented out in the *-compose.yml files if required.
82
+
The quickstart script will configure, build, and start the ANMS system for the first time. See comments in the script for additional details, including optional ENV variables to override default behavior.
79
83
84
+
To stop the system use `podman compose -f testenv-compose.yml -f docker-compose.yml down`.
80
85
81
-
## ANMS build and deploy
86
+
To start the system in the future use `podman compose -f testenv-compose.yml up`and `podman compose up`.
82
87
88
+
## Manual Startup
83
89
Choose the appropriate docker, podman or podman-compose commands in the directions below as appropriate for your system.
84
90
85
-
- Select appropriate profile(s) as desired.
86
-
- If no profiles are set, a "light" deployment of the ANMS focused on browser-less API-only ANMS users.
87
-
- For a full deployment: `export COMPOSE_PROFILES=full`
88
-
- For a full deployment with additional developer tools: `export COMPOSE_PROFILES=full,dev`
91
+
- Edit `.env` file as appropriately
92
+
- Select appropriate profile(s) as desired.
93
+
- Core ANMS services are always started.
94
+
- The 'full' profile starts up all UI and related services.
95
+
- The 'dev' profile adds development tools, such as adminer
96
+
- Profiles can be set with COMPOSE_PROFILES in the .env file. The default includes full and dev profiles.
97
+
- Adjust network ports as necessary to avoid any conflicts or permissions issues.
98
+
- For rootless podman, the AUTHNZ_* ports must be changed to higher number ports to avoid permissions issues.
99
+
- The corresponding lines can be uncommented in .env.
100
+
- SELinux Security Labels Setup
101
+
- If your system does not support security labels, no additional steps are needed.
102
+
- If security labels are supported and you are unable to define them, they can be disabled for development purposes:
@@ -126,11 +140,11 @@ To restart the system, use the 'up' and 'down' commands as described in the prev
126
140
127
141
The top-level `docker-compose.yml` uses the environment defined by the sibling file `.env`. Note: If using the legacy/deprecated build.sh script, that script may additionally override some environment variables.
128
142
129
-
Two principal options of the compose configuration, which are both defaulted to empty text, are:
143
+
The principal options of the compose configuration are:
130
144
131
145
*`DOCKER_IMAGE_PREFIX` which controls any image name prefix added to all ANMS images.
132
146
For a local build, this can be left empty, but for builds intended to be pushed to a Docker image registry this can be set to the full path on the registry before the image names (e.g. `DOCKER_IMAGE_PREFIX=some.host.example.com:5000/path/to/images`).
133
-
147
+
*`HOST_SOCKDIR` which controls the source of the bind mount on `amp-manager` container for its transport socket. This can either be a volume name, for inter-container or non-root user use, or an absolute path on the host filesystem, used in the production deployment.
0 commit comments