Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Action fails to start with failure on ssh.sock #78

Closed
verdverm opened this issue May 2, 2024 · 3 comments
Closed

Action fails to start with failure on ssh.sock #78

verdverm opened this issue May 2, 2024 · 3 comments

Comments

@verdverm
Copy link

verdverm commented May 2, 2024

Behaviour

Steps to reproduce this issue

Recently updated to the latest version

  1. Try and use action on a macos-latest runner

Expected behaviour

Should install like it used to

Actual behaviour

Tell us what happens instead

{"level":"debug","msg":"executing ssh for exiting the master: /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/Users/runner/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^[email protected],[email protected]\" -o User=runner -o ControlMaster=auto -o ControlPath=\"/Users/runner/.lima/docker-actions-toolkit/ssh.sock\" -o ControlPersist=yes -O exit -p 49206 127.0.0.1]","time":"2024-05-02T03:34:35Z"}
{"error":"failed to execute `ssh -O exit -p 49206 127.0.0.1`, out=\"Control socket connect(/Users/runner/.lima/docker-actions-toolkit/ssh.sock): No such file or directory\\r\\n\": exit status 255","level":"warning","msg":"failed to exit SSH master","time":"2024-05-02T03:34:35Z"}
{"level":"info","msg":"Shutting down QEMU with ACPI","time":"2024-05-02T03:34:35Z"}
{"error":"dial unix /Users/runner/.lima/docker-actions-toolkit/qmp.sock: connect: connection refused","level":"warning","msg":"failed to open the QMP socket \"/Users/runner/.lima/docker-actions-toolkit/qmp.sock\", forcibly killing QEMU","time":"2024-05-02T03:34:35Z"}
{"level":"info","msg":"QEMU has already exited","time":"2024-05-02T03:34:35Z"}

Configuration

https://github.com/hofstadter-io/hof/blob/update-cue/.github/workflows/hof.yml#L49

runs-on: macos-latest
...
      - name: Set up Docker
        uses: crazy-max/ghaction-setup-docker@v3
        with:
          version: v24.0.7
        env:
          SIGN_QEMU_BINARY: "1"
          COLIMA_START_ARGS: --cpus 3 --memory 10 --disk 12
        if: ${{ startsWith( runner.os, 'macos') }}

Logs

https://github.com/hofstadter-io/hof/actions/runs/8917966055/job/24491846313#step:6:297

@verdverm
Copy link
Author

verdverm commented May 2, 2024

This might be related to the macos-latest now being M1 based?

@verdverm
Copy link
Author

verdverm commented May 2, 2024

linking because others are seeing similar in other context, might be helpful: ReactiveCircus/android-emulator-runner#350

@crazy-max
Copy link
Owner

This might be related to the macos-latest now being M1 based?

Yes this related to #53

See disclaimer in the README:

> [!WARNING]
> Does not work on macOS runners with ARM architecture (no nested virtualization):
> * https://github.com/crazy-max/ghaction-setup-docker/pull/53
> * https://github.com/docker/actions-toolkit/issues/317
![Screenshot](.github/setup-docker-action.png)

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

No branches or pull requests

2 participants