search

tcardonne / docker-github-runner

Run GitHub Actions on self-hosted runner using Docker.
MIT License
297 stars 124 forks source link

Unrecognized command-line input arguments: 'token' #11

Closed patrickelectric closed 4 years ago

patrickelectric commented 4 years ago

When running docker: 

Exchanging the GitHub Access Token with a Runner Token...
curl: (22) The requested URL returned error: 404 Not Found
Unrecognized command-line input arguments: 'token'. For usage refer to: .\config.cmd --help or ./config.sh --help
tcardonne commented 4 years ago

Hi,

It seems your RUNNER_REPOSITORY_URL environment variable is incorrect. Could you double-check ? It should be something like https://github.com/tcardonne/docker-github-runner.

If you still have the issue, could you provide more details ? (docker command, docker-compose.yml and your variables, make sure to hide sensitive variables).

patrickelectric commented 4 years ago

Hi Thomas,

It turns out that my problem was the token, it was necessary to select all the options under the repo section to make it valid and work. Maybe an error message could help with that when running the docker.

Besides that, it's working without problems, thanks !

On Sat, Apr 4, 2020 at 7:54 AM Thomas Cardonne notifications@github.com wrote:

Hi,

It seems your RUNNER_REPOSITORY_URL environment variable is incorrect. Could you double-check ? It should be something like https://github.com/tcardonne/docker-github-runner.

If you still have the issue, could you provide more details ? (docker command, docker-compose.yml and your variables, make sure to hide sensitive variables).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tcardonne/docker-github-runner/issues/11#issuecomment-609011018, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJIYCPTKCALT6BC3F7KVC3RK4GVLANCNFSM4L47FQPA .

-- Patrick José Pereira Electronics Engineer Skype: patrickelectric434 IRC: patrickelectric +55 (048) 99917-4777

tcardonne commented 4 years ago

I'll add a condition after the API call to check if the token was successfuly created or not, and give better diagnosis than the raw curl message.

Thanks for the feedback!

cepefernando commented 3 years ago

I ended up creating a new GitHub Access Token with full permissions on my account, that was all the problem.