Level=fatal msg="version control system not configured"

Drone Support
1

I’m able to login with GitHub Oauth just fine, I have the following server/agent config below(I’m using the Kontena.io platform):
level=fatal msg=“version control system not configured”

I don’t expect anyone to be familiar with Kontena’s stack yml definition, but perhaps someone can glance through the following and let me know if I’m missing any required info to get the server/agent up and running with github

services:
server:
image: drone/drone:latest
instances: 1
stateful: true
deploy:
strategy: ha
wait_for_port: 80
links:
- ${LB_NAME}
environment:
- DRONE_GITHUB=true
- DRONE_SERVER_ADDR=0.0.0.0:80
- DRONE_OPEN=true
- DATABASE_DRIVER=sqlite3
- DATABASE_CONFIG=/var/lib/drone/drone.sqlite
- KONTENA_LB_VIRTUAL_HOST=${LB_VIRTUAL_HOST}
secrets:
- secret: DRONE_GITHUB_CLIENT_ID
name: DRONE_GITHUB_CLIENT
type: env
- secret: DRONE_GITHUB_CLIENT_SECRET
name: DRONE_GITHUB_SECRET
type: env
- secret: DRONE_SHARED_SECRET
name: DRONE_AGENT_SECRET
type: env
- secret: DRONE_ADMIN_USERNAMES
name: DRONE_ADMIN
type: env
volumes:
- /var/lib/drone

agent:
image: drone/drone:latest
stateful: no
instances: ${AGENT_INSTANCES}
depends_on:
- server
environment:
- DRONE_SERVER=http://reaction.boomerdigital.net:80
secrets:
- secret: DRONE_SHARED_SECRET
name: DRONE_SECRET
type: env
- secret: DRONE_HOST
name: DRONE_HOST
type: env
volumes:
- /var/run/docker.sock:/var/run/docker.sock
command: agent

2

version control system not configured

Please change your configuration to use drone/drone:0.7 instead of drone/drone:latest

The reason you are receiving this error is that you are installing a newer, pre-release version of drone by using the :latest tag. This version has different configuration instructions. Specifically we have split the server and agent into two separate images.

If you intend to use the latest, pre-release version of drone you will need to configure it accordingly. For more information please see our draft release notes:
http://docs.drone.io/release-0.8.0

1 Like
3

@dhonig I’m not sure if this is related to your issue but I can see the following issues

  1. drone/drone:0.7 (server) needs DRONE_HOST setup like https://drone.whatever.com probably http://reaction.boomerdigital.net in your case
  2. I’ve never used the DRONE_SERVER_ADDR so I’m not sure if you need that
  3. agent should be drone/drone:0.7 (FYI for if you’re using latest) agent needs to be drone/agent image since drone and agent are now two different images for the server and agent.
  4. I use DRONE_SECRET not DRONE_AGENT_SECRET but maybe both of those env vars work on the server
  5. I don’t know if it’s required but I also have the DRONE_ORGS set to the github orgs I allow to have access when it’s open the way you have it.
1 Like