Here are listed some recommendations when deploying Aspire using the container images.
Official container images:
- docker.repository.sca.accenture.com/docker/aspire:5.0 (online distribution)
- docker.repository.sca.accenture.com/docker/aspire-basic:5.0 (offline distribution)
The official docker image provided with Aspire assumes Internet connectivity for downloading the jar files needed for the different connectors and components on Aspire.
If running with the official container image, it is recommended to provide a volume pointing to
/opt/aspire/.m2/repository on all containers for the jars to be downloaded only once, otherwise if restarted, the container would download all the jar files again.
If you are running the service locally and deploying to your local .m2 repository, you could provide:
So your containers can see what you install locally when running "
mvn clean install" on your aspire components
Login to artifactory docker registry:
You'll need to use your registered email/password credentials.
For production deployments it is recommended to create a custom Aspire image, containing all the jar files needed for the deployment to run. This way no new downloads will be required during restarts and uptime will be improved.
There is an official docker image of aspire containing all the basic components jar files, only missing the premium components ones. Those premium jar files must be downloaded and added to your custom aspire image manually.
You'll need to have Maven 3 installed, and configured to use https://repository.sca.accenture.com/artifactory/public as the repository. Follow Configuring Maven for Aspire.
Change directory to your image folder
For each premium component you'll need to execute: (where VERSION is 5.0, 5.0.1, 5.0.2, etc, and COMPONENT-ARTIFACT-ID is the maven artifact id of the component)
Should be called "Dockerfile"
docker build -t [image-name]:[image-tag] .