Containerization Introduction

Elastic Path Self-Managed Commerce is most often run in Docker-style containers. To enable this, Elastic Path provides and supports tools for building Elastic Path Commerce container images.

Overview

Elastic Path provides two different ways of running Self-Managed Commerce with containers.

The information in this section is for customers who develop their own infrastructure solution. It provides the information about building and running Elastic Path Self-Managed as containers in your own containerized environment.

note

Elastic Path also provides tooling that provides container build, infrastructure deployment, and container deployment tools, as an alternative to implementing your own. For more information about the options, see Elastic Path Commerce Infrastructure Options.

Containerization Tooling

Elastic Path provides and supports tools for building Elastic Path Commerce container images. This tooling is available in a separate Git repository and includes:

• Entrypoint scripts that support the various configuration options of the Elastic Path Commerce applications.
• Scripts for building Elastic Path Commerce container images.
• Scripts for building ActiveMQ container images. ActiveMQ is a required component of the Elastic Path Commerce stack.
• Scripts for building MySQL database container images. MySQL is the relational database system that is most-often used with Elastic Path Commerce. The MySQL container is suitable for development and testing purposes.
• Examples of running Elastic Path Commerce services and processes as containers, in the form of Docker Compose files.

Containerization Tooling Releases

The containerization tooling is released in a separate Git repository named docker, and is updated and released at a different cadence from the Commerce ep-commerce project.

To access the tooling, first ensure that you have access to the Elastic Path code.elasticpath.com server then navigate to the Elastic Path Commerce docker git repository. Licensed customers are given access. If you do not have access, see Code and Artifacts.

The different releases of the docker containerization tooling are available as separate branches of the Git project. Elastic Path recommends regularly updating to the latest available release by applying patches and deploying new releases as they become available.

For information about compatibility between Commerce ep-commerce releases and docker containerization tooling releases, see Compatibility.

For the change history of the docker containerization tooling project, see CHANGELOG.