How does Drone replace docker-compose [Pending status forever]

Drone Support
1

Hi guys, im new on this awesome tool. But i still dont understund how to run it properly…

I have experience with Docker/docker-compose.

dockerfile-compose
dockerfile-compose1552×1428 162 KB

But now… with Drone i dont understand that those two files dont exist anymore ? Or how can i integrate them ?

I have a .drone.yml file with this:

workspace:
  base: .
  path: /opt/src/
pipeline:
  hyper-cool-app:
    image: node:6.10.0-slim
    commands:
      - npm install
      - npm run build
      - npm run serve
    branches: master

But… build status stays on “PENDING” forever

2

I would like to help, but this post lacks a clear description of the problem, logs, sample configurations and relevant steps to reproduce. These details are required in order to effectively provide support.

Which two files? I am having difficulty understanding this.

When a build is pending forever it almost always means you have not configured your agent correctly. Did you install drone per the documentation? Do you see anything in your server or agent logs indicating there is a problem?

3

The Build Queue

queue
queue1552×1122 118 KB

The Build List

buildlist
buildlist1552×510 41.5 KB

My Drone Config

version: '3'

services:
  drone-server:
    image: drone/drone:0.7
    network_mode: bridge
    ports:
      - 8080:8000
    volumes:
      - /var/lib/drone:/var/lib/drone/
    restart: always
    environment:
      - DRONE_ADMIN=cristiandley
      - DRONE_OPEN=true
      - DRONE_HOST=172.21.1.112:8080
      - DRONE_BITBUCKET=true
      - DRONE_BITBUCKET_CLIENT=somecoolclient
      - DRONE_BITBUCKET_SECRET=somecoolsecret
      - DRONE_SECRET=3cb25600077b2264bd00038c058d9000
  drone-agent:
    image: drone/drone:0.7
    network_mode: bridge
    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=3cb25600077b2264bd00038c058d9000

docker-compose logs

drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host
drone-agent_1 | rpc: error re-connecting: dial tcp: lookup drone-server on 8.8.8.8:53: no such host

The only detail i see is the docker logs… trying 8.8.8.8:53. Away from that i cant see anything weird… :frowning_face:

4

This indicates the agent is failing to connect to your server. Because the agent cannot connect with the server, it cannot run any builds. This is why all builds sit in a pending state.

The error message lookup drone-server on 8.8.8.8:53: no such host indicates there are network issues and dns lookup issues in your docker environment. These issues indicate a problem with your docker installations and configuration or host machine configuration.

5

well i tested some configs and i cant repair this ( i used the default nginx conf, that the tutorial offers)

rpc: error re-connecting: dial tcp <my-External-Ip>:80: getsockopt: connection timed out
rpc: error re-connecting: dial tcp <my-External-Ip>:80: getsockopt: connection timed out
rpc: error re-connecting: dial tcp <my-External-Ip>:80: getsockopt: connection timed out
rpc: error re-connecting: dial tcp <my-External-Ip>:80: getsockopt: connection timed out
rpc: error re-connecting: dial tcp <my-External-Ip>:80: getsockopt: connection timed out

and if i use insted of drone-server my local ip

pipeline: request next execution
pipeline: received next execution: 1
rpc: error making call: jsonrpc2: code 0 message: sql: no rows in result set
pipeline: error signaling pipeline init: 1: jsonrpc2: code 0 message: sql: no rows in result set
rpc: error making call: jsonrpc2: code 0 message: sql: no rows in result set
Pipeine: error updating pipeline step status: 1: clone: jsonrpc2: code 0 message: sql: no rows in result set

im sorry about my noobness

6

Okey… it worked… dont know what happen.

Seems that it dindt liked my external ip ?