Autoscaling Gitlab runner doesn't use the existing docker

I have setup Gitlab ci autoscale runner on scaleway hosting using docker+machine. I am finding that the setup spawns new machines and when it’s not in use it doesn’t remove those machines but just shut them down. But when a new job comes in it tries to connect to the shutdown machine, but finds that they are down and will try to spawn a new machine. A new machine will not get spawned as it approaches the limit of the number of machines that it is allowed to make. So after a while, my CI is stuck.

So my question is, sorry if it sounds trivial, is this how the system is supposed to work? Is the issuing machine not getting deleted or the machine not being able to be restarted?

concurrent = 4
check_interval = 0

  name = "Autoscale docker - scaleway"
  url = ""
  token = "<token>"
  executor = "docker+machine"
  limit = 4
    tls_verify = false
    image = "ruby:2.1"
    privileged = false
    disable_cache = false
    volumes = ["/cache"]
    shm_size = 0
    IdleCount = 2
    IdleTime = 600
    MachineDriver = "scaleway"
    MachineName = "auto-scale-%s"
    MachineOptions = [
    MaxBuilds = 10
    OffPeakTimezone = "Asia/Calcutta"
    OffPeakIdleCount = 1
    OffPeakIdleTime = 1200
    OffPeakPeriods = [               # Set the Off Peak time mode on for:
      "* * 0-9,18-23 * * mon-fri *", # - Monday to Friday for 12am to 9am and 6pm to 11pm
      "* * * * * sat,sun *"          # - whole Saturday and Sunday

Hi coderhs,

I also use a ‘docker+machine’ runner on a scaleway DEV1-S server. I can execute jobs on it but it spawns a new machine on each job run. Used machines are in ‘archived’ state but not automatically removed. I tweaked concurrent, limit, IdleCount, IdleTime gitlab-runner options with no effect. :frowning:

Did you solve the problem?

If yes, I’m interested in your feedback