Own gitlabrunner in aws

Hi,
I installed my own gitlabrunner on a EC2 instance at aws.
It is running there: “sudo service gitlab-runner status” gives me
gitlab-runner (pid 7313) is running…

Version info:

$ gitlab-runner --version
Version: 11.2.0
Git revision: 35e8515d
Git branch: 11-2-stable
GO version: go1.8.7
Built: 2018-08-22T15:57:53+00:00
OS/Arch: linux/amd64

In the gitlab-UI I also see the runner. But with a warn triangle: “New runner. Has not connected yet.”
When I start my test-jobs this gitlabrunner is never chosen regardless of its type specific or shared.

I also tagged the runner with a specific label and my project too(same label). But still the own runner is not chosen. What do I wrong?

BTW: The sestatus command gives:
SELinux status: disabled

I mention this because I found a post that this behavior has its reason in a enables selinux.

I updated now to version 11.5.0 from gitlab-runner…

Here are some information from /var/log/messages:
Nov 23 08:13:34 ip-172-31-34-210 gitlab-runner[6274]: Running in system-mode. #033[0;m
Nov 23 08:13:34 ip-172-31-34-210 gitlab-runner[6274]: #033[0;m
Nov 23 08:13:34 ip-172-31-34-210 gitlab-runner[6274]: Configuration loaded #033[0;m builds#033[0;m=0
Nov 23 08:13:34 ip-172-31-34-210 gitlab-runner[6274]: Listen address not defined, metrics server disabled#033[0;m builds#033[0;m=0
Nov 23 08:13:34 ip-172-31-34-210 gitlab-runner[6274]: Listen address not defined, session server disabled#033[0;m builds#033[0;m=0
Nov 23 08:15:48 ip-172-31-34-210 gitlab-runner[6274]: #033[0;33mWARNING: Requested service stop: terminated #033[0;m #033[0;33mbuilds#033[0;m=0
Nov 23 08:15:48 ip-172-31-34-210 gitlab-runner[6274]: All workers stopped. Can exit now #033[0;m builds#033[0;m=0
Nov 23 08:17:47 ip-172-31-34-210 gitlab-runner[17006]: Starting multi-runner from /etc/gitlab-runner/config.toml …#033[0;m builds#033[0;m=0
Nov 23 08:17:47 ip-172-31-34-210 gitlab-runner[17006]: Running in system-mode. #033[0;m
Nov 23 08:17:47 ip-172-31-34-210 gitlab-runner[17006]: #033[0;m
Nov 23 08:17:47 ip-172-31-34-210 gitlab-runner[17006]: Configuration loaded #033[0;m builds#033[0;m=0
Nov 23 08:17:47 ip-172-31-34-210 gitlab-runner[17006]: Listen address not defined, metrics server disabled#033[0;m builds#033[0;m=0
Nov 23 08:17:47 ip-172-31-34-210 gitlab-runner[17006]: Listen address not defined, session server disabled#033[0;m builds#033[0;m=0
Nov 23 08:17:47 ip-172-31-34-210 gitlab-runner[17006]: #033[0;33mWARNING: Failed to update executor docker+machine for ea44db1e Missing Machine options#033[0;m
Nov 23 08:17:50 ip-172-31-34-210 gitlab-runner[17006]: #033[0;33mWARNING: Failed to update executor docker+machine for ea44db1e Missing Machine options#033[0;m
Nov 23 08:17:53 ip-172-31-34-210 gitlab-runner[17006]: #033[0;33mWARNING: Failed to update executor docker+machine for ea44db1e Missing Machine options#033[0;m

And my /etc/gitlab-runner/config.toml looks like:

concurrent = 1
check_interval = 0

[session_server]
session_timeout = 1800

[[runners]]
name = “ct-frontend”
url = “https://gitlab.com
token = “…xxx”
executor = “docker+machine”
[runners.docker]
tls_verify = false
image = “alpine:latest”
privileged = false
disable_entrypoint_overwrite = false
oom_kill_disable = false
disable_cache = false
volumes = ["/cache"]
shm_size = 0
[runners.cache]
[runners.cache.s3]
[runners.cache.gcs]
[runners.machine]
IdleCount = 0
MachineDriver = “”
MachineName = “”
OffPeakTimezone = “”
OffPeakIdleCount = 0
OffPeakIdleTime = 0

Please help.

First success. My mistake was to specify docker+machine as executor. I only need docker. (I did not install docker machine.) Now I re-registered the runnner with executor “docker” and it starts…