github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #5615] [MERGED] chore(docs): add note about docker requirements for macos #14363

New Issue
Closed
opened 2026-04-13 09:26:17 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 09:26:17 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/5615
Author: @jonathansamines
Created: 10/27/2025
Status: ✅ Merged
Merged: 10/27/2025
Merged by: @himself65

Base: canary ← Head: docs/add-docker-macos-notes

📝 Commits (1)

  • 12ee015 docs: add note about docker requirements for macos

📊 Changes

1 file changed (+3 additions, -0 deletions)

View changed files

📝 CONTRIBUTING.md (+3 -0)

📄 Description

While trying to get my environment up and running (docker containers), I had the mssql continously failing with the following error:

<jemalloc>: (This is the expected behaviour if you are running under QEMU)
/opt/mssql/bin/sqlservr: Invalid mapping of address 0x400534d000 in reserved address space below 0x400000000000. Possible causes:
1) the process (itself, or via a wrapper) starts-up its own running environment sets the stack size limit to unlimited via syscall setrlimit(2);
2) the process (itself, or via a wrapper) adjusts its own execution domain and flag the system its legacy personality via syscall personality(2);
3) sysadmin deliberately sets the system to run on legacy VA layout mode by adjusting a sysctl knob vm.legacy_va_layout.

Turns out, this is because mssql does not officially support macos so Rosetta emulation is currently necessary as a short term workaround. So adding a note about that.

Summary by cubic

Added a macOS note to the Docker setup in CONTRIBUTING.md: the mssql container likely needs Rosetta emulation and at least 2GB RAM. This helps prevent startup failures and links to Microsoft’s container prerequisites.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/5615 **Author:** [@jonathansamines](https://github.com/jonathansamines) **Created:** 10/27/2025 **Status:** ✅ Merged **Merged:** 10/27/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `docs/add-docker-macos-notes` --- ### 📝 Commits (1) - [`12ee015`](https://github.com/better-auth/better-auth/commit/12ee0154d63f0efbf66b0adb5daef78407149953) docs: add note about docker requirements for macos ### 📊 Changes **1 file changed** (+3 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `CONTRIBUTING.md` (+3 -0) </details> ### 📄 Description While trying to get my environment up and running (docker containers), I had the `mssql` continously failing with the following error: ```bash <jemalloc>: (This is the expected behaviour if you are running under QEMU) /opt/mssql/bin/sqlservr: Invalid mapping of address 0x400534d000 in reserved address space below 0x400000000000. Possible causes: 1) the process (itself, or via a wrapper) starts-up its own running environment sets the stack size limit to unlimited via syscall setrlimit(2); 2) the process (itself, or via a wrapper) adjusts its own execution domain and flag the system its legacy personality via syscall personality(2); 3) sysadmin deliberately sets the system to run on legacy VA layout mode by adjusting a sysctl knob vm.legacy_va_layout. ``` Turns out, this is because `mssql` does not officially support `macos` so Rosetta emulation is currently necessary as a short term workaround. So adding a note about that. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Added a macOS note to the Docker setup in CONTRIBUTING.md: the mssql container likely needs Rosetta emulation and at least 2GB RAM. This helps prevent startup failures and links to Microsoft’s container prerequisites. <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 09:26:17 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#14363
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?