Docker compose examples need extra property for Apple M4
Nobody has claimed this yet.
- #31466 by @jdcmsd — closed without merging
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
New Apple M4 chipset causes a crash when trying to run our default Docker Compose YAMLs.
Steps to Reproduce
Run docker compose up from new hardware.
Acceptance Criteria
The following environment property seems to solve the problem in a backwards-compatible way:
JAVA_TOOL_OPTIONS: "-XX:UseSVE=0"
See discussion in Slack thread, below. @oidacra and I both tested it out on our M1s with no issue.
dotCMS Version
latest (25.02.24)
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Slack thread:
https://dotcms.slack.com/archives/C028Z3R2D/p1740417815932829?thread\_ts=1740417749.517759&cid=C028Z3R2D
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running docker compose up with the repository's default Docker Compose YAMLs on affected Apple hardware and inspect the Slack discussion linked in the issue. Update the relevant Compose examples with the proposed JAVA_TOOL_OPTIONS property, then confirm startup on Apple M4 and that existing hardware remains compatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, java
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100