- 03 Dec 2025
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
Roll-Back Polarity Updates
- Updated on 03 Dec 2025
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
This process applies to the Polarity Server v5 with containerized PostgreSQL and Redis services.
There has been some limited success in applying this process in the following cases due to individualized variations in the database components:
Servers that have been updated from Polarity v4
Servers that use an external service for PostgreSQL
In the cases listed above, we recommend contacting Polarity Support for assistance PRIOR to attempting an upgrade. Feel free to reach out to Support@Polarity.io for support or any questions you may have.
Prepare
This process will apply tags to the desired images so that they are easily referenced.
Check the image IDs of the loaded Docker images, and note the image IDs of the Polarity Platform and Web images.
See the command below to get the information you need.
Example: Polarity Platform v5.4.2 image ID:
eaf0aa9bc33eExample: Polarity Web UI v5.4.3 image ID:
926ab167816f
Apply new image tags to the Polarity Platform and Web images to more easily refer to them.
Use the following command:
docker image tag <image_ID> <image_name>:<image.version>
Examples:
docker image tag eaf0aa9bc33e polarity_platform:5.4.2docker image tag 926ab167816f polarity_web:5.4.3
Verify the image tags just added using the command from Step 1.
There may be duplicate entries for the same image(s). This is just an artifact of adding a new tag to an existing image. These point to the same image, and aren’t physically duplicated (ie. they don’t take up extra disk space).
Steps to Roll Back
This process overwrites the image loaded by default with the image desired.
Bring down the Polarity Server (if it is running).
cd /app && ./down.sh
Open the
/app/docker-compose.ymlfile for editing.Find the lines specifying the
imagefor the “app" and “web" containers.These will be in the
servicesblock.
Comment out the
imageline for each container.The “pound sign” or “hashtag” is used to denote comments in YAML files.
For example, change from this (truncated view):
. . . volumes: - polarity_platform_local_postgres:/var/lib/postgresql/data:Z app: image: 577326318091.dkr.ecr.us-east-1.amazonaws.com/polarity-aws-prod/polarity_platform:latest container_name: polarity_platform . . . max-size: "10M" max-file: "6" web: image: 577326318091.dkr.ecr.us-east-1.amazonaws.com/polarity-aws-prod/web:latest container_name: polarity_web . . .…to this:
. . . volumes: - polarity_platform_local_postgres:/var/lib/postgresql/data:Z app: # image: 577326318091.dkr.ecr.us-east-1.amazonaws.com/polarity-aws-prod/polarity_platform:latest container_name: polarity_platform . . . max-size: "10M" max-file: "6" web: # image: 577326318091.dkr.ecr.us-east-1.amazonaws.com/polarity-aws-prod/web:latest container_name: polarity_web . . .
Add in new
imagelines that point to the image tags created for the images we want to roll back to:. . . volumes: - polarity_platform_local_postgres:/var/lib/postgresql/data:Z app: # image: 577326318091.dkr.ecr.us-east-1.amazonaws.com/polarity-aws-prod/polarity_platform:latest image: polarity_platform:5.4.2 container_name: polarity_platform . . . max-size: "10M" max-file: "6" web: # image: 577326318091.dkr.ecr.us-east-1.amazonaws.com/polarity-aws-prod/web:latest image: polarity_web:5.4.3 container_name: polarity_web . . .Save the file and close it.
Bring the Polarity Server up.
cd /app && ./up.sh
Verify the expected version is running.
cd /app && ./health_check.sh
Test the functionality of the Polarity Server.
Log into the Polarity Server.
Install or Update an integration.
Tests the connection to the Polarity Store and the installed certificates.
Conduct a search using an integration that reaches out to a remote data source.
The SANS Internet Storm Center (ISC) integration is a simple, free option.
This tests the full chain interaction from the UI thru the back end, plus the connection out and back to an external data source.
Follow-On Notes
This process simply changes the image that loads by default to the one specified on the
imageline.It does not delete any images from the system.
Future updates will overwrite the
imageline with the line given in the installer.
Useful Commands
Useful command to check image info:
for i in $(docker image ls --format="{{.ID}}" | uniq)
do
echo "Image ID: $i"
docker image inspect $i | jq '.[].Config.Labels | "\(.name) v\(.version)"'; docker image inspect $i | jq '.[].RepoTags|.[]'
echo
doneOne-liner version of the above:
for i in $(docker image ls --format="{{.ID}}" | uniq); do echo "Image ID: $i"; docker image inspect $i | jq '.[].Config.Labels | "\(.name) v\(.version)"'; docker image inspect $i | jq '.[].RepoTags|.[]'; echo; doneSample output from the above command:
Image ID: 07784203dc39
"Polarity Platform v5.5.2"
"577326318091.dkr.ecr.us-east-1.amazonaws.com/polarity-aws-prod/polarity_platform:latest"
Image ID: 829deb91d60f
"Polarity Platform Web UI v5.5.0"
"577326318091.dkr.ecr.us-east-1.amazonaws.com/polarity-aws-prod/web:latest"
Image ID: eaf0aa9bc33e
"Polarity Platform v5.4.2"
Image ID: 926ab167816f
"Polarity Platform Web UI v5.4.3"
"577326318091.dkr.ecr.us-east-1.amazonaws.com/polarity-web/dev:latest"
Image ID: 43724892d6db
"null vnull"
"redis:latest"
Image ID: 27c7d7de1cc7
"null vnull"
"577326318091.dkr.ecr.us-east-1.amazonaws.com/polarity-aws-prod/postgres-ip4r:latest"Other Useful Docker Commands
List all images: docker images