Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Pilot Lvl 1
Message 1 of 9

Self-hosted runners and services (not working)

Solved! Go to Solution.

I have installed a self-hosted runner on my mac to try it, but it always failed to run at the point of initiating a service

 

 

Screen Shot 2019-11-06 at 2.55.16 PM.png

 

Screen Shot 2019-11-06 at 2.55.05 PM.png

 

Is this normal? or with self-hosted runners, I should also not sue services and try to use docker instead?

 

Thanks

 

 

 

------------------------

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

8 Replies
Highlighted
Pilot Lvl 1
Message 2 of 9

Re: Self-hosted runners and services (not working)

Any update about this one? I can't seem to find any mention in the documentation that using services with self-hosted actions won't work.

------------------------

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Highlighted
Community Manager
Message 3 of 9

Re: Self-hosted runners and services (not working)

Hi @linuxjuggler,

 

Thanks for being here and our sincere apologies for the delayed response, are you still having this issue?


Best,
AndreaG

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Highlighted
Pilot Lvl 1
Message 4 of 9

Re: Self-hosted runners and services (not working)

I didn't try it anymore since no one confirmed that they have fixed it.

 

@AndreaGriffiths11 Can you confirm it is working and fixed?

 

 

 

------------------------

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Highlighted
Pilot Lvl 1
Message 5 of 9

Re: Self-hosted runners and services (not working)

 

Screen Shot 2019-12-29 at 5.12.45 PM.png

 

From what I can tell this is not working, and the best option is to depend on using local docker (docker-compose or Dockerfile) instead of depending on the services with self-hosted version!

 

So to answer your question @AndreaGriffiths11 : sadly, Yes I am still facing the same issue.

 

https://github.com/linuxjuggler/local-actions/commit/d409b98a312fa2e576d7ce0ddf8a5bede722133a/checks...

 

 

 

 

------------------------

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Highlighted
GitHub Staff
Message 6 of 9

Re: Self-hosted runners and services (not working)

We currently only support container operations on Linux Runners.

Services, which use docker containers, will not work on OSX or Windows.

 

This error message is not particularly helpful, we have a PR in place to address the error message which has not been rolled out yet: https://github.com/actions/runner/pull/221

 

We have also passed along feedback to the team that supporting containers on non-Linux Runners would be helpful. You may also create an enhancement issue in the actions runner repo linked above.

 

Highlighted
Pilot Lvl 1
Message 7 of 9

Re: Self-hosted runners and services (not working)

Thanks @thboop for the reply.

Just to be clear, if I run the self hosted runner on Linux services should work without any problems right?

------------------------

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Highlighted
Solution
GitHub Staff
Message 8 of 9

Re: Self-hosted runners and services (not working)

@linuxjuggler correct!

You will need to make sure docker is installed on the self hosted runner's machine and in the path.

 

I was able to verify this was working earlier today, if you have access to a linux box, you can test this with the following workflow after setting up a self hosted runner:

 

name: Test CI

on: [push, pull_request]

jobs:
  test:
    services:
      redis:
        image: redis
        ports:
          - 6379/tcp
    runs-on: ["self-hosted", "Linux"]
    steps:
    - run: docker ps

We can see the output from the step below, where the redis image is running in docker.

 

2020-01-06T21:12:05.7169898Z CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                  PORTS                     NAMES
2020-01-06T21:12:05.7171418Z 01d4c9dc666f        redis               "docker-entrypoint.s…"   1 second ago        Up Less than a second   0.0.0.0:32773->6379/tcp   803c3ff666ca429781c69a13e9e8160c_redis_6dea08
2020-01-06T21:12:05.7358695Z Stop and remove container: 803c3ff666ca429781c69a13e9e8160c_redis_6dea08

 

Highlighted
Pilot Lvl 1
Message 9 of 9

Re: Self-hosted runners and services (not working)

I'll do thanks @thboop 

 

 

------------------------

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!