woodpecker-ci / woodpecker

Woodpecker is a simple, yet powerful CI/CD engine with great extensibility.
https://woodpecker-ci.org
Apache License 2.0
4.07k stars 353 forks source link

Example Config for agent with an external Srever? #2619

Closed orsenthil closed 10 months ago

orsenthil commented 10 months ago

Component

agent

Describe the bug

I have a server and agent running on different machines.

I don't find any examples of agent only configuration that I can point to the woodpecker server.

I have tried this.

# docker-compose.yml
version: '3'

services:
  woodpecker-agent:
    image: woodpeckerci/woodpecker-agent:v0.15.4
    command: agent
    restart: always
    environment:
      - WOODPECKER_SERVER=ci.server.com:9000
      - WOODPECKER_AGENT_SECRET="SECRET"
      - WOODPECKER_DEBUG=true
      - WOODPECKER_BACKEND=docker

I get two different kinds of errors.

woodpecker-agent_1  | {"level":"error","error":"rpc error: code = Unavailable desc = connection closed before server preface received","time":"2023-10-21T19:20:12Z","message":"grpc error: done(): code: Unavailable: rpc error: code = Unavailable desc = connection closed before server preface received"}

and

woodpecker-agent_1  | {"level":"error","error":"rpc error: code = Unavailable desc = connection closed before server preface received","time":"2023-10-23T00:51:47Z","message":"grpc error: done(): code: Unavailable: rpc error: code = Unavailable desc = connection closed before server preface received"}

System Info

source  "https://github.com/woodpecker-ci/woodpecker"
version "1.0.3"

Additional context

No response

Validations

qwerty287 commented 10 months ago

Since I didn't try something like this, I can only guess what you could do:

anbraten commented 10 months ago

Make sure you use v1.0 or next, but most importantly the same version for agent and server. Also you don't need command: agent and WOODPECKER_BACKEND=docker, but you are missing to mount the docker socket to your agent