robertefreeman

Runner configuration when using a self-signed certificate

Using self-signed certificates is not recommended due to the configuration required on the runner to support them. If you do need to use a self-signed certificate, you will need to configure the certificate on each runner.

The correct steps for configuring the self-signed certificate will depend on how it is generated, and the platforms and technologies used on your runners (which may validate the certificate in different ways).

Some tips for successfully configuring self-signed certificates are included below. These steps can be taken before or after registering the runner.

Install the certificate

robertefreeman

version: '3.4'

services:

  wordpress:
    image: arm32v7/wordpress
    ports:
      - 80:80
    environment:
      WORDPRESS_DB_PASSWORD: wordpress

robertefreeman

version: '3.6'

services:

  mq:
    image: arm32v7/rabbitmq:3-management
    ports:
      - 5672:5672
      - 15672:15672
    hostname: rabbit

robertefreeman

version: '3.6'

services:

  portainer:
    image: portainer/portainer:linux-arm
    ports:
      - 9000:9000
    deploy:
      placement:

robertefreeman

Keybase proof

I hereby claim:

• I am robertxfreeman on github.
• I am robertefreeman (https://keybase.io/robertefreeman) on keybase.
• I have a public key ASBYJ293za7iVlxT4jIJz9lrLJNC2CCAybz0qNQURxNMxwo

To claim this, I am signing this object:

robertefreeman

Keybase proof

I hereby claim:

• I am robertxfreeman on github.
• I am robertefreeman (https://keybase.io/robertefreeman) on keybase.
• I have a public key ASBYJ293za7iVlxT4jIJz9lrLJNC2CCAybz0qNQURxNMxwo

To claim this, I am signing this object: