[PR #1416] [MERGED] Add user level Docker socket to common paths #1934

New issue

Closed

opened 2026-03-01 21:53:18 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 21:53:18 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/nektos/act/pull/1416
Author: @bendrucker
Created: 10/29/2022
Status: ✅ Merged
Merged: 10/29/2022
Merged by: @mergify[bot]

Base: master ← Head: patch-1

📝 Commits (1)

ffe6c38 Add user level Docker socket to common paths

📊 Changes

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

View changed files

📝 cmd/root.go (+1 -0)

📄 Description

In v4.13.0, Docker for Mac stopped providing /var/run/docker.sock, resulting in act failing on macOS. By default, it listens on ~/.docker/run/docker.sock instead.

This was a breaking change in a non-major release and a rollback is planned:

https://github.com/docker/for-mac/issues/6529#issuecomment-1292135881

This PR adds the new socket path to the bugReport output. Hopefully seeing that the user-level socket is available will help users set DOCKER_HOST rather than filing a report.

In the long run, it sounds like Docker wants people to move away from hardcoding a Docker host, default or otherwise, in their clients. docker context list will return the user's configured endpoints.

See #1411

_{🔄 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/nektos/act/pull/1416 **Author:** [@bendrucker](https://github.com/bendrucker) **Created:** 10/29/2022 **Status:** ✅ Merged **Merged:** 10/29/2022 **Merged by:** [@mergify[bot]](https://github.com/apps/mergify) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`ffe6c38`](https://github.com/nektos/act/commit/ffe6c38abab46b71513996081011948530e7a531) Add user level Docker socket to common paths ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `cmd/root.go` (+1 -0) </details> ### 📄 Description In v4.13.0, Docker for Mac stopped providing `/var/run/docker.sock`, resulting in `act` failing on macOS. By default, it listens on `~/.docker/run/docker.sock` instead. This was a breaking change in a non-major release and a rollback is planned: https://github.com/docker/for-mac/issues/6529#issuecomment-1292135881 This PR adds the new socket path to the `bugReport` output. Hopefully seeing that the user-level socket is available will help users set `DOCKER_HOST` rather than filing a report. In the long run, it sounds like Docker wants people to move away from hardcoding a Docker host, default or otherwise, in their clients. `docker context list` will return the user's configured endpoints. See #1411 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>