Can't run a Cilicon via Gitlab runner (Citadel.SSHClient.CommandFailed error 1.)

[kpolupanova]

Hi! I've tried to start workin with cilicon and get an error that I can't figure out how to fix.
After launc Cilicon i get this error:
Configuring GitLab Runner...�
The operation couldn’t be completed. (Citadel.SSHClient.CommandFailed error 1.)

here is my cilicon.yml

source: oci://ghcr.io/cirruslabs/macos-sonoma-xcode:15.3
provisioner:
  type: gitlab
  config:
    gitlabURL: https://gitlab.com
    runnerToken: <runner_token>

Could somebody tell me what I'm doing wrong ?

[Marcocanc]

Hi @kpolupanova, to rule out potential issues with the gitlab provisioner, could you test with a script type provisioner and just echo "hello world"?

[kpolupanova]

@Marcocanc Thanks for fast answer! With scrip it's goint like this. Is it correct behaviour ? I've set up CI/CD and trying to figure out how to run my pipeline by virtual machine.
Should I create new runner for Cilicon or use existing is fine ?
At local machine all works correctly with runner that i use for Cilicon.

[Marcocanc]

The behaviour with script seems to be fine.
Unfortunately I personally don't have a gitlab account and can't test with it. I will try to set up an account soon though.

Should I create new runner for Cilicon or use existing is fine ?
At local machine all works correctly with runner that i use for Cilicon.

Could you explain this a bit further with more context? Do I understand it correctly, that you are able to spin up a gitlab runner on your local machine with the same runner token you were trying to use in Cilicon?

[kpolupanova]

Could you explain this a bit further with more context? Do I understand it correctly, that you are able to spin up a gitlab runner on your local machine with the same runner token you were trying to use in Cilicon?

Sure!

Well, I've tried set up Cilicon with new gitlab runner that was't registred at all at Host OS machine, and got the same error, then tried to set up Cilicon with existing runner token that was registred at Host OS machine.
So I have same result in each variant and doesn't understand how I need to do it propertly.

And after all, for being sure that i don't have any problem with runner with same token, I checked that runner work correctly at Host OS machine.

[janckoch]

I have the same Problem here. I am trying to connect the cilicon runner to a self-hosted gitlab instance and i end up in an endless loop with the aforementioned error

The cilicon.yml is
source: oci://ghcr.io/cirruslabs/macos-sonoma-xcode:15.4
provisioner:
type: gitlab
config:
gitlabURL: <gitlab_url>
runnerToken: <runner_token>

And the cilicon version is 2.2.2

[alanrickman]

I'm seeing the same behaviour as described above. My cilicon.yml looks like this:

source: oci://ghcr.io/cirruslabs/macos-sonoma-xcode:15.3
provisioner:
 type: gitlab
 config:
   gitlabURL: https://xxxx
   runnerToken: glrt-xxxxx

It seems like the issue was introduced in Cilicon v2.2.1. The runner successfully connects to GitLab if I downgrade to v2.2.0.

[kpolupanova]

@alanrickman thanks for your reply, I'll try with a downgrade, and hope that this issue will be fixed in future release