In the transition from Aria Config to Tanzu Salt, some users may require the ability to test deployments, etc. These are instructions for how to manually import the provided Docker image
Aria Config 8.16+
Tanzu Salt 8.10+
SaltStack - all versions
Aria Config has been rebranded as Tanzu Salt and is now part of the Tanzu Platform. Tanzu Platform uses container images to deploy software within the stack instead of traditional RPM packages.
.tar.gz
file).gunzip raas-<version>.tar.gz
.docker load -i raas-<version>.tar
.http://localhost:8080
./etc/raas/raas
to listen on the external interface./etc/raas
to the new host configuration directory.raas.config
from the unpacked tar.gz file to the host configuration directory.raas.config
to raas
.localhost:8080
.docker run --restart unless-stopped -d --name raas -p 8080:8080 \
-v <path to raas config directory>:/etc/raas \
-v <path to raas logs directory>:/var/log/raas \
-v <path to raas cache directory>:/var/cache/raas \
-v <path to raas fileserver directory>:/srv \
<image tag>:<version>
docker run --restart unless-stopped -d --name raas -p 8080:8080 \
-v /opt/raas/config:/etc/raas \
-v /opt/raas/log:/var/log/raas \
-v /opt/raas/cache:/var/cache/raas \
-v /opt/raas/srv:/srv \
raas:8.18.0.20
curl http://localhost:8080
.root/salt
(new installation) or existing credentials (upgrades).docker exec -ti <container id> bash
.su -p raas
.raas save_creds
and provide credentials for Postgres and Redis.sv restart raas
..tar.gz
file.gunzip raas-<new version>.tar.gz
docker load -i raas-<new version>.tar
docker stop raas
.docker rm raas
.docker run --restart unless-stopped -d --name raas -p 8080:8080 \
-v <path to raas config directory>:/etc/raas \
-v <path to raas logs directory>:/var/log/raas \
-v <path to raas cache directory>:/var/cache/raas \
-v <path to raas fileserver directory>:/srv \
<image tag>:<new version>
docker rmi <image tag>:<old version>
Note: Downgrades are not supported. Using an older container version after a newer one has run will result in a mismatch between the database and RaaS versions.
If you have an existing RaaS server with configurations, and SSL already setup, then it's possible to follow the steps above to install Docker and import the container. You will not require the reverse proxy for SSL termination. You simply update the container run command to include the additional mount to the /etc/pki directory as follows
docker run --restart unless-stopped -d --name raas -p 443:443 \
-v <path to raas config directory>:/etc/raas \
-v <path to raas logs directory>:/var/log/raas \
-v <path to raas cache directory>:/var/cache/raas \
-v <path to raas fileserver directory>:/srv \
-v <path to pki directory:/etc/pki \
<image tag>:<new version>
Assuming your configuration is already setup to look at this directory for TLS certificates, then the daemon should start right up and be listening on port 443.