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

Error: Container action is only supported on Linux #75

Open
adamjsturge opened this issue Sep 26, 2024 · 3 comments
Open

Error: Container action is only supported on Linux #75

adamjsturge opened this issue Sep 26, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@adamjsturge
Copy link

Describe the bug
Unable to run shoutrrr on macos pipelines

To Reproduce
Steps to reproduce the behavior:

name: Test Action
on:
  pull_request:
  workflow_dispatch:

jobs:
  testjob:
    timeout-minutes: 60
    runs-on: macos-latest
    steps:
      - uses: actions/checkout@v4
      - name: Notify on Fail
        uses: containrrr/shoutrrr-action@v1
        with:
          url: ${{ secrets.SHOUTRRR_URL }}
          title: "Test Action"
          message: "This action could work"

Expected behavior
Would like it not to crash and work on macos

@adamjsturge adamjsturge added the bug Something isn't working label Sep 26, 2024
@arnested
Copy link
Member

Oh! Container actions are only supported on Linux. I did not know that.

Getting the action to run on macOS would really be nice.

But this would require a quite different approach, then. Maybe a Node.js app downloading and executing the right Shoutrrr binary.

Perhaps someone implemented this approach somewhere else so we can be inspired or reuse parts.

@arnested arnested self-assigned this Nov 14, 2024
@arnested
Copy link
Member

Or just a composite action, downloading the tool. Probably a lot simpler.

@arnested
Copy link
Member

But upstream releases (https://github.com/containrrr/shoutrrr/releases/tag/v0.8.0) lack a macOS build.

And we want to avoid building the tool during the run of the action.

Hmmm... Not sure what the best approach forward is...

Until we figure out what to do I'll stick a notice in the readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants