With the docker v29 release, this action may fail on self hosted runners (and potentially gh runners too?)

[JCMais]

Starting single-node Redis instance: --name redis --publish 6379:6379 --detach redis:7.2.3
docker: Error response from daemon: client version 1.40 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer >version.
See 'docker run --help'.

To fix it for us I forked the action and made this change: JCMais@7a4a8c9

I can open a PR with the same change, but looks like the repo is not mantained anymore?

[marcuspoehls]

@JCMais Hey Jonathan, I would very much appreciate a pull request. I prefer to use the latest tag instead of stable or a specific version, like 28.

FROM docker:latest

Are you fine with that and would you send a PR?

[Michal-Szczepaniak]

Hi, I've encountered this exact issue today, and @JCMais's version works just fine. Could this be fixed perhaps? Thanks

[marcuspoehls]

@Michal-Szczepaniak Hey Michał, this should be fixed since version 1.8.1.

    - name: Start Redis
      uses: supercharge/redis-github-action@1.8.1

[Michal-Szczepaniak]

It's not, i tried it on 1.8.1, hence i'm writing to you :)

[marcuspoehls]

Interesting. Thanks for pointing this out. I recently updated to 1.8.1 after running into the issue and didn’t have a problem. I’m using GitHub’s runners and didn’t look any further after a green pipeline.

I don’t want to tuck Docker to version 28, I would like to use the latest Docker version available to be forward-compatible. But maybe there are situations where a runner is using an older version and that causes issues.

[Michal-Szczepaniak]

I'm using runs-on: ubuntu-24.04 tried ubuntu-latest, same thing. I don't know how to explain it mate, probably github messed something up

[marcuspoehls]

I’ll keep an eye on it. Maybe there’s something I didn’t see.

[jl54]

For me it worked after updating to 1.8.1 on ubuntu-latest