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
During Anylog deployment we noticed that when we update POSTGRES_IMAGE_TAG in .bashrc, the change doesn't seem to be represented in the deployment
Steps:
In ~/.bashrc update POSTGRES_IMAGE_TAG=16.0
source ~/.bashrc
Deploy OpenHorizon (which includes Postgres)
Expect: PSQL v16.0
Actual: PSQL v13.0 (default)
The text was updated successfully, but these errors were encountered:
ericaquaronne
changed the title
When we update POSTGRES_IMAGE_TAG in .bashrc, the change does not get represented in the deployment (AnyLog)
When we update POSTGRES_IMAGE_TAG in .bashrc, the change does not get represented in the deployment (AnyLog testing)
Sep 11, 2024
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
...
91f6ba68b302 postgres:16.0 "docker-entrypoint.s…" 10 minutes ago Up 3 minutes (healthy) 0.0.0.0:5432->5432/tcp, :::5432->5432/tcp postgres
6d32f6a737c1 postgres:16.0 "docker-entrypoint.s…" 10 minutes ago Up 3 minutes (healthy) 0.0.0.0:5433->5432/tcp, [::]:5433->5432/tcp postgres-fdo-owner-service
During Anylog deployment we noticed that when we update POSTGRES_IMAGE_TAG in
.bashrc
, the change doesn't seem to be represented in the deploymentSteps:
In ~/.bashrc update POSTGRES_IMAGE_TAG=16.0
source ~/.bashrc
Deploy OpenHorizon (which includes Postgres)
Expect: PSQL v16.0
Actual: PSQL v13.0 (default)
The text was updated successfully, but these errors were encountered: