Drone 0.7 bad handshake

Drone Support
1

Hey guys,

im trying to setup Drone for my Gogs instance.
Thats my docker-compose

version: '2'

services:
  drone-server:
    image: drone/drone:0.7
    volumes:
      - /var/lib/drone:/var/lib/drone/
    restart: always
    environment:
      - DRONE_OPEN=true
      - DRONE_HOST=${DRONE_HOST}
      - DRONE_GOGS=true
      - DRONE_GOGS_URL=https://domain.de
      - DRONE_SECRET=${DRONE_SECRET}

  drone-agent:
    image: drone/drone:0.7
    command: agent
    restart: always
    depends_on:
      - drone-server
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - DRONE_SERVER=ws://drone-server:8000/ws/broker
      - DRONE_SECRET=${DRONE_SECRET}

When i try to start it with docker-compose up im recieving the following errors again and again

drone-server_1  | Unable to connect agent. Invalid authorization token "Bearer" does not match ""
drone-agent_1   | rpc: error re-connecting: websocket: bad handshake

Sombody has an idea how to fix this?

Thank you guys

2

This error message tells me that DRONE_SECRET is not being properly set. Both the server and agent seem to have a blank value. It is required that you provide the server and agent with a shared secret key, of your own choosing, for authentication.

3

Thank you @bradrydzewski this fixed my problem.

But now im recieving the message:
drone-agent_1 | pipeline: request next execution

Nothing happens now. When i try to access the url im reciveing an error so the service is not startet.

Now my kernel gives me some messages:
kernel:[392135.516128] unregister_netdevice: waiting for lo to become free. Usage count = 1

What did i do wrong?

4

No clue. This error message has never been reported before. If I had to guess, I would say it has something to do with your host machine network configuration, but debugging kernel issues is outside my area of expertise.

5

I googled the error and according to stack overflow and a number of issues in the docker forum, it seems to be a kernel issue and not related to drone.

I therefore recommend working with the docker support forum to find a fix.