Axon Ivy Engine
1M+
The images in this repository contain the Axon Ivy Engine, which are based on official Eclipse Temurin images.
Maintained by:
Axon Ivy
Where to get help:
Axon Ivy Community
Where to file issues:
GitHub
Supported architectures:
amd64, arm64
Axon Ivy is a Process Automation Platform that simplifies and automates the interaction of humans with their digital systems. The platform is typically responsible for the most precious business cases where companies produce value.
You can start an Axon Ivy Engine with a single command:
docker run -p 8080:8080 axonivy/axonivy-engine:12.0
Checkout our docker samples for more examples.
For production environments, you should use a specific version tag, such as 12.0.9, instead of a floating tag. This ensures you always know exactly which version of the Axon Ivy Engine is running and prevents unexpected upgrades when new images are published.
A minor version tag, such as 12.0, always points to the latest patch release within that release train. While this is convenient for development and testing, it is not recommended for production, as your deployment may automatically pick up newer Axon Ivy Engine patch versions without notice.
Tags such as milestone, nightly and dev provide access to pre-release builds. They let you try out the latest features and fixes that are planned for an upcoming Axon Ivy Engine release before they become generally available.
The axonivy/axonivy-engine image is available in several variants, each tailored to a specific use case.
axonivy/axonivy-engine:<version>This is the default image and the recommended choice for most use cases. If you're unsure which variant to use, start with this one. It is based on Ubuntu and includes all the features required to run the Axon Ivy Engine.
axonivy/axonivy-engine:<version>-slimThis variant is identical to the default image, except that it does not include the demo-portal application or the bundled OpenSearch instance.
It is the recommended choice for production environments, where the demo-portal is unnecessary. Running OpenSearch as a separate container is also considered a best practice, as it allows you to manage, scale, and upgrade it independently of the Axon Ivy Engine.
axonivy/axonivy-engine:<version>-alpineThis variant provides the same features as the default image but is based on Alpine instead of Ubuntu. It includes everything required to run the Axon Ivy Engine while offering a smaller base image.
axonivy/axonivy-engine:<version>-alpine-slimThis variant is identical to the alpine based image, except that it does not include the demo-portal application or the bundled OpenSearch instance.
It is the recommended choice for production environments, where the demo-portal is unnecessary. Running OpenSearch as a separate container is also considered a best practice, as it allows you to manage, scale, and upgrade it independently of the Axon Ivy Engine.
Content type
Image
Digest
sha256:0a6a3d5b1…
Size
319 MB
Last updated
about 5 hours ago
docker pull axonivy/axonivy-engine