Skip to content

fix(install): mount the Docker socket inside the VM on macOS - #1190

Open
thedavididris wants to merge 1 commit into
Tencent:mainfrom
thedavididris:fix/macos-docker-socket
Open

thedavididris wants to merge 1 commit into
Tencent:mainfrom
thedavididris:fix/macos-docker-socket

Conversation

@thedavididris

Copy link
Copy Markdown

On macOS the Docker daemon runs in a Linux VM (Docker Desktop, colima, OrbStack, Rancher Desktop) and resolves bind mount sources there. The installer saved the context endpoint, the Mac-side forward of the socket, as LOOPFORGE_DOCKER_SOCKET, so the platform container failed to start with "mkdir ...docker.sock: operation not supported". On macOS it now saves /var/run/docker.sock, where the daemon listens inside the VM.

A rerun replaces a Mac-side value that an earlier install saved, which otherwise stayed in .env and broke every later start. A socket the operator set to any other path is kept. Linux keeps the context endpoint, so rootless Docker is unchanged.

Fixes #1161

Claude-Session: https://claude.ai/code/session_01DVYzcPse64U1k6Y8Segmyt

What changed

Describe the user problem and the resulting behavior.

Scope

  • Platform core / API / runner
  • Public adapter / deployment
  • Classic
  • Portable
  • Shared behavior contract
  • Installer / CLI
  • Documentation only

Compatibility

List affected hosts and any migration or backward-compatibility impact.

Validation

List commands that were actually run and mark anything blocked or not run.

go test -p=2 ./... -count=1 -timeout=180s
go vet ./...
python3 scripts/check-public.py
bash local/scripts/validate.sh
bash local/scripts/smoke-install.sh
bash local/scripts/e2e.sh
bash scripts/scan-secrets.sh

Safety

  • I did not include credentials, internal endpoints, production data, or organization-specific infrastructure.
  • I preserved user files and unrelated changes.
  • I updated generated Classic host bundles when applicable.
  • I documented third-party content and licensing changes when applicable.

On macOS the Docker daemon runs in a Linux VM (Docker Desktop, colima,
OrbStack, Rancher Desktop) and resolves bind mount sources there. The
installer saved the context endpoint, the Mac-side forward of the socket,
as LOOPFORGE_DOCKER_SOCKET, so the platform container failed to start with
"mkdir ...docker.sock: operation not supported". On macOS it now saves
/var/run/docker.sock, where the daemon listens inside the VM.

A rerun replaces a Mac-side value that an earlier install saved, which
otherwise stayed in .env and broke every later start. A socket the operator
set to any other path is kept. Linux keeps the context endpoint, so rootless
Docker is unchanged.

Fixes Tencent#1161
@thedavididris
thedavididris force-pushed the fix/macos-docker-socket branch from 042bd24 to 72da120 Compare November 21, 2026 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: macOS 安装把宿主机侧的 Docker socket 写入 .env,平台容器无法启动

1 participant