title: Gitlab Runner - listen_address not defined
body: <p>I am setting up gitlab-runner locally on my mac to be able to run build and test scripts using docker. I have gone through the installation instructions listed on the Gitlab runners page to install the runner locally:</p>
  <pre><code># Download the binary for your system
  sudo curl --output /usr/local/bin/gitlab-runner https://gitlab-runner-downloads.s3.amazonaws.com/latest/binaries/gitlab-runner-darwin-amd64
  
  # Give it permissions to execute
  sudo chmod +x /usr/local/bin/gitlab-runner
  
  # The rest of commands execute as the user who will run the Runner
  # Register the Runner (steps below), then run
  cd ~
  gitlab-runner install
  gitlab-runner start
  </code></pre>
  <p>From what I can tell it is installed fine. I then registered a runner like so:</p>
  <pre><code>sudo gitlab-runner register --url https://gitlab.com/ --registration-token $REGISTRATION_TOKEN
  </code></pre>
  <p>(I obviously replaced <code>$REGISTRATION_TOKEN</code> with my token). When it prompts me for additional details I have entered the following:</p>
  <ul>
  <li>Tags: (I left this blank)</li>
  <li>Enter an executor: <code>docker</code></li>
  <li>Enter the default docker image: <code>node:14.0.0</code></li>
  </ul>
  <p>I then get the following message:</p>
  <blockquote>
  <p>Runner registered successfully. Feel free to start it, but if it's
  running already the config should be automatically reloaded!</p>
  </blockquote>
  <p>When I then navigate to the root of my project I try and run gitlab-runner run but I get the following error:</p>
  <pre><code>Starting multi-runner from /Users/ben/.gitlab-runner/config.toml...  builds=0
  WARNING: Running in user-mode.                     
  WARNING: Use sudo for system-mode:                 
  WARNING: $ sudo gitlab-runner...                   
                                                     
  Configuration loaded                                builds=0
  listen_address not defined, metrics &amp; debug endpoints disabled  builds=0
  [session_server].listen_address not defined, session endpoints disabled  builds=0
  ^CWARNING: [runWait] received stop signal             builds=0 stop-signal=interrupt
  WARNING: Graceful shutdown not finished properly    builds=0 error=received stop signal: interrupt
  WARNING: Starting forceful shutdown                 StopSignal=interrupt builds=0
  All workers stopped. Can exit now                   builds=0
  </code></pre>
  <p>When I look at the config.toml if looks like it may be missing some configuration in there as the error above may suggest? Here is a cat of the entire file:</p>
  <pre><code>concurrent = 1
  check_interval = 0
  
  [session_server]
    session_timeout = 1800
  </code></pre>
  <p>I'm not sure why i'm receiving this error message? Does my config look alright? When searching the issue I found another thread that said to just set &quot;Can run untagged jobs&quot; to yes which I have done but it still does not work...</p>