Local Development on M1/M2 Apple Macs

Starting with Engine 4.1 release and newer, you don’t need to apply this special tag in the releases anymore. All releases 4.1 and after are published as universal images contain CPU-architecture specific contents in the same image. Read more about this in PageBuilder Engine Universal Docker Images announcement.

When using M1/M2 (arm) architecture hardware for development environments, you must add a small special instruction to environment variables.

The PageBuilder Engine team creates separate docker images with M1/M2 support for each engine version for local development. To run Fusion on Apple M1/M2s, you must choose and define which engine version you’re using on your local development environment. This means, when there is a new Engine release, updating this environment variable is necessary to start using new features and fixes coming with the new version of Engine releases. Set the following in your .env file:

FUSION_RELEASE=[engine-version]-arm

Pick and set [engine-version] in this example like 3.3.4-arm Ensure you don’t have duplicate FUSION_RELEASE set anywhere else in your .env file.

Use -m1 Suffix prior to Engine 4.0.1 and Engine 3.3.6 releases

Starting with Engine 4.0.1 and 3.3.6 releases, we switched to using -arm suffix instead of -m1 in favor of broader arm CPU architecture.