\n\ni did attempt `pull_5323-alpine` as recomended in #5238 but it didnt work. the pod never stood up.\n\n### Steps to reproduce\n\n1. install woodpecker (using longhorn as a storage backend and forgejo as a forge but that hasnt been an issue before) on k3s cluster.\n2. create pipeline.\n3. attempt to run it.\n4. will never complete pod creation.\n\n### Expected behavior\n\ncreates pod, and run pipeline\n\n### System Info\n\n```shell\nsource\t\"https://github.com/woodpecker-ci/woodpecker\"\nversion\t\"3.8.0\"\n```\n\n### Additional context\n\n\u003Cimg width=\"1875\" height=\"143\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/6fbbcd41-751c-4d5d-b852-f05e57d6ca12\" />\n\n\u003Cimg width=\"1008\" height=\"312\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/6fc6001e-01e4-4cce-b9c4-2ccc144b9b1a\" />\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[3061],{"name":3018,"color":3019},5345,"Kubernetes Pod never completes initialisation - hangs forever","2025-07-21T14:12:00Z","https://github.com/woodpecker-ci/woodpecker/issues/5345",0.6883792,{"description":3068,"labels":3069,"number":3071,"owner":3021,"repository":3022,"state":3072,"title":3073,"updated_at":3074,"url":3075,"score":3076},"### Component\n\nagent\n\n### Describe the bug\n\nAgents after running a while starts throwing error and restarting. Auto-restart from k8s does not fix the issue, only deleting the pod.\n\n\n\n### Steps to reproduce\n\nIt just happens after few minutes of idle.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n$ kubectl version\nClient Version: v1.31.5\nKustomize Version: v5.4.2\nServer Version: v1.31.5+k3s1\n\n\nMy helmfile configuration as follows. In logs above you can see 3.3.0 instead of 3.2.0 as I tried to manually upgrade agent to see if newer version fixes the issue or not.\n\n\nrepositories:\n - name: woodpecker\n url: https://woodpecker-ci.org/\n skipTLSVerify: true\n\nreleases:\n - name: woodpecker-server\n chart: woodpecker/woodpecker\n version: 2.1.0\n namespace: woodpecker\n createNamespace: true\n cleanupOnFail: false\n devel: false\n installed: true\n skipDeps: false\n values:\n - server:\n env:\n WOODPECKER_ADMIN: admin\n WOODPECKER_HOST: https://cicd\n WOODPECKER_GITHUB: false\n WOODPECKER_GITEA: true\n WOODPECKER_GITEA_URL: https://git\n WOODPECKER_AUTHENTICATE_PUBLIC_REPOS: true\n # WOODPECKER_LOG_LEVEL: trace\n \n extraSecretNamesForEnvFrom:\n - woodpecker-gitea-client\n - woodpecker-gitea-secret\n - woodpecker-secret\n \n persistentVolume:\n storageClass: \"local-path\"\n \n ingress:\n enabled: true\n annotations:\n cert-manager.io/cluster-issuer: letsencrypt\n hosts:\n - host: cicd\n paths:\n - path: /\n pathType: Prefix\n tls:\n - secretName: cicd-tls\n hosts:\n - cicd\n - agent:\n resources:\n limits:\n cpu: 500m\n memory: 512Mi\n requests:\n cpu: 100m\n memory: 64Mi\n env:\n WOODPECKER_SERVER: \"woodpecker-server.woodpecker.svc.cluster.local:9000\"\n WOODPECKER_BACKEND_K8S_STORAGE_CLASS: \"local-path\"\n WOODPECKER_BACKEND_K8S_STORAGE_RWX: \"false\"\n WOODPECKER_FORGE_TIMEOUT: \"30s\"\n WOODPECKER_MAX_WORKFLOWS: \"3\"\n```\n\n### Additional context\n\n```\n$ kubectl -n woodpecker get pods\nNAME READY STATUS RESTARTS AGE\nwoodpecker-server-0 1/1 Running 0 46h\nwoodpecker-server-agent-0 0/1 CrashLoopBackOff 77 (2m2s ago) 6h21m\nwoodpecker-server-agent-1 0/1 CrashLoopBackOff 77 (3m6s ago) 6h21m\n\n$ kubectl -n woodpecker delete pod woodpecker-server-agent-0\npod \"woodpecker-server-agent-0\" deleted\n\n$ kubectl -n woodpecker get pods\nNAME READY STATUS RESTARTS AGE\nwoodpecker-server-0 1/1 Running 0 46h\nwoodpecker-server-agent-0 0/1 ContainerCreating 0 2s\nwoodpecker-server-agent-1 0/1 CrashLoopBackOff 77 (3m33s ago) 6h22m\n\n$ kubectl -n woodpecker get pods\nNAME READY STATUS RESTARTS AGE\nwoodpecker-server-0 1/1 Running 0 46h\nwoodpecker-server-agent-0 1/1 Running 1 (4s ago) 7s\nwoodpecker-server-agent-1 0/1 CrashLoopBackOff 77 (3m38s ago) 6h22m\n```\nLogs before restart:\n```\n{\"level\":\"info\",\"time\":\"2025-03-05T13:40:32Z\",\"message\":\"log level: info\"}\n{\"level\":\"info\",\"time\":\"2025-03-05T13:40:32Z\",\"message\":\"starting Woodpecker agent with version '3.3.0' and backend 'kubernetes' using platform 'linux/amd64' running up to 3 pipelines in parallel\"}\npanic: runtime error: invalid memory address or nil pointer dereference\npanic: runtime error: invalid memory address or nil pointer dereference\n[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1a40389]\n\ngoroutine 73 [running]:\ngo.woodpecker-ci.org/woodpecker/v3/pipeline/backend/kubernetes.(*kube).DestroyWorkflow(0x34d87e0, {0x2364440, 0xc0000bc9b0}, 0xc000283680, {0xc0002dc998, 0x4})\n/src/pipeline/backend/kubernetes/kubernetes.go:428 +0x109\ngo.woodpecker-ci.org/woodpecker/v3/pipeline.(*Runtime).Run.func1()\n/src/pipeline/pipeline.go:112 +0x7f\npanic({0x1d11040?, 0x349eb10?})\n/usr/local/go/src/runtime/panic.go:787 +0x132\ngo.woodpecker-ci.org/woodpecker/v3/pipeline/backend/kubernetes.(*kube).SetupWorkflow(0x34d87e0, {0x2364440, 0xc0000bc9b0}, 0xc000283680, {0xc0002dc998, 0x4})\n/src/pipeline/backend/kubernetes/kubernetes.go:194 +0xa3\ngo.woodpecker-ci.org/woodpecker/v3/pipeline.(*Runtime).Run(0xc000258d20, {0x2364440, 0xc0000bc9b0})\n/src/pipeline/pipeline.go:118 +0x2eb\ngo.woodpecker-ci.org/woodpecker/v3/agent.(*Runner).Run(0xc000068a80, {0x2364440, 0xc0000bc9b0}, {0x23643d0, 0x34fc7e0})\n/src/agent/runner.go:153 +0xeb3\ngo.woodpecker-ci.org/woodpecker/v3/cmd/agent/core.run.func5()\n/src/cmd/agent/core/agent.go:293 +0x205\ngolang.org/x/sync/errgroup.(*Group).Go.func1()\n/src/vendor/golang.org/x/sync/errgroup/errgroup.go:78 +0x50\ncreated by golang.org/x/sync/errgroup.(*Group).Go in goroutine 1\n/src/vendor/golang.org/x/sync/errgroup/errgroup.go:75 +0x93\n```\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[3070],{"name":3018,"color":3019},4934,"closed","Runtime SIGSEGV error in agent","2025-03-14T13:04:55Z","https://github.com/woodpecker-ci/woodpecker/issues/4934",0.6453065,{"description":3078,"labels":3079,"number":3083,"owner":3021,"repository":3022,"state":3072,"title":3084,"updated_at":3085,"url":3086,"score":3087},"### Component\r\n\r\nagent, maybe?\r\n\r\n### Describe the bug\r\n\r\nToday I'm trying woodpecker, on a RaspberryPI I found in a drawer, both server and agent on the same raspi.\r\n\r\nI connected it to a gitea and everything went smoothly but one thing: the agent were not picking tasks.\r\n\r\nMy `.woodpecker.yml` looks like:\r\n\r\n```yml\r\n---\r\n\r\npipeline:\r\n test:\r\n image: debian\r\n commands:\r\n - echo Hello from Woodpecker\r\n```\r\n\r\nIn order for the agent to pick job I had to add:\r\n\r\n```diff\r\n+platform: linux/arm64\r\n```\r\n\r\nI expected that, without telling the platform explicitly, any agent would pick it, so it would be picked by the only agent I have.\r\n\r\nIt looks like this:\r\n\r\n\r\n\r\nThe one on the top is the one with an explicit `platform`, it gets picked and run. The one in the bottom don't have an explicit `platform` setting and never gets picked (and no information is given about why it's not picked ☹).\r\n\r\n\r\n\r\n\u003Cdetails>\r\n\u003Csummary>\r\nThe logs when I'm not specifying the `platform`\r\n\u003C/summary>\r\n\r\n```text\r\nwoodpecker-agent_1 | {\"level\":\"trace\",\"error\":\"rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \\\"error reading from server: EOF\\\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \\\"too_many_pings\\\"\",\"time\":\"2022-12-08T08:43:20Z\",\"message\":\"grpc: to many keepalive pings without sending data\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:43:21Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/grpc/rpc.go:63\",\"message\":\"agent connected: 04c8d295e8f3: polling\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:43:21Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:321\",\"message\":\"queue: pending right now: 16\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:43:21Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:293\",\"message\":\"queue: trying to assign task: 16 with deps []\"}\r\nwoodpecker-agent_1 | {\"level\":\"trace\",\"error\":\"rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \\\"error reading from server: EOF\\\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \\\"too_many_pings\\\"\",\"time\":\"2022-12-08T08:44:41Z\",\"message\":\"grpc: to many keepalive pings without sending data\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:44:42Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/grpc/rpc.go:63\",\"message\":\"agent connected: 04c8d295e8f3: polling\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:44:42Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:321\",\"message\":\"queue: pending right now: 16\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:44:42Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:293\",\"message\":\"queue: trying to assign task: 16 with deps []\"}\r\nwoodpecker-agent_1 | {\"level\":\"trace\",\"error\":\"rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \\\"error reading from server: EOF\\\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \\\"too_many_pings\\\"\",\"time\":\"2022-12-08T08:47:22Z\",\"message\":\"grpc: to many keepalive pings without sending data\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:47:23Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/grpc/rpc.go:63\",\"message\":\"agent connected: 04c8d295e8f3: polling\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:47:23Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:321\",\"message\":\"queue: pending right now: 16\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:47:23Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:293\",\"message\":\"queue: trying to assign task: 16 with deps []\"}\r\nwoodpecker-agent_1 | {\"level\":\"trace\",\"error\":\"rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \\\"error reading from server: EOF\\\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \\\"too_many_pings\\\"\",\"time\":\"2022-12-08T08:52:43Z\",\"message\":\"grpc: to many keepalive pings without sending data\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:52:44Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/grpc/rpc.go:63\",\"message\":\"agent connected: 04c8d295e8f3: polling\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:52:44Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:321\",\"message\":\"queue: pending right now: 16\"}\r\nwoodpecker-server_1 | {\"level\":\"debug\",\"time\":\"2022-12-08T08:52:44Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:293\",\"message\":\"queue: trying to assign task: 16 with deps []\"}\r\nwoodpecker-agent_1 | {\"level\":\"trace\",\"error\":\"rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \\\"error reading from server: EOF\\\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \\\"too_many_pings\\\"\",\"time\":\"2022-12-08T09:03:24Z\",\"message\":\"grpc: to many keepalive pings without sending data\"}\r\n```\r\n\u003C/details>\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"0.15.5\"}\r\n\r\n\r\non\r\n\r\n```text\r\nLinux raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux\r\n```\r\n\r\nusing `docker-compose`.\r\n```\r\n\r\n### Validations\r\n\r\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\r\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[3080],{"name":3081,"color":3082},"feedback","4B7070",1468,"With a single arm64 agent: jobs are not pulled without an explicit `platform:`.","2022-12-25T08:52:03Z","https://github.com/woodpecker-ci/woodpecker/issues/1468",0.65685385,{"description":3089,"labels":3090,"number":3092,"owner":3021,"repository":3022,"state":3072,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### Component\n\nagent\n\n### Describe the bug\n\nWe were running Woodpecker v2.1.1 on Kubernetes backend at a multi-node cluster on AWS.\r\n\r\nWe've got a few `panic: runtime error` logs in our agent like this:\r\n\r\n```\r\npanic: runtime error: invalid memory address or nil pointer dereference\r\n[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x16f7594]\r\n\r\ngoroutine 99699 [running]:\r\n[go.woodpecker-ci.org/woodpecker/v2/pipeline/backend/kubernetes.(*kube).WaitStep(0xc00050a140](http://go.woodpecker-ci.org/woodpecker/v2/pipeline/backend/kubernetes.%28*kube%29.WaitStep%280xc00050a140), {0x1e32748, 0xc0005048c0}, 0xc00116c500?, {0xc0024529b0, 0x5})\r\n /src/pipeline/backend/kubernetes/kubernetes.go:251 +0x594\r\n[go.woodpecker-ci.org/woodpecker/v2/pipeline.(*Runtime).exec(0xc001d80b80](http://go.woodpecker-ci.org/woodpecker/v2/pipeline.%28*Runtime%29.exec%280xc001d80b80), 0xc00116c500)\r\n /src/pipeline/pipeline.go:269 +0x196\r\n[go.woodpecker-ci.org/woodpecker/v2/pipeline.(*Runtime).execAll.func1()](http://go.woodpecker-ci.org/woodpecker/v2/pipeline.%28*Runtime%29.execAll.func1%28%29)\r\n /src/pipeline/pipeline.go:206 +0x1ba\r\n[golang.org/x/sync/errgroup.(*Group).Go.func1()](http://golang.org/x/sync/errgroup.%28*Group%29.Go.func1%28%29)\r\n /src/vendor/[golang.org/x/sync/errgroup/errgroup.go:75](http://golang.org/x/sync/errgroup/errgroup.go:75) +0x56\r\ncreated by [golang.org/x/sync/errgroup.(*Group).Go](http://golang.org/x/sync/errgroup.%28*Group%29.Go) in goroutine 41\r\n /src/vendor/[golang.org/x/sync/errgroup/errgroup.go:72](http://golang.org/x/sync/errgroup/errgroup.go:72) +0x96\r\n```\r\n\r\nTracking it down to https://github.com/woodpecker-ci/woodpecker/blob/v2.1.1/pipeline/backend/kubernetes/kubernetes.go#L251 it's likely that either `ContainerStatuses` is empty or Terminated is nil, both which would cause a panic.\r\n\r\nNow it seems that simply adding error handling code either case would be a viable option here, which is what I did internally (and I hope to be submitting that for review shortly). This way we were able to track down at least one occurrence of the bug: when the node hosting the pod is killed before the agent can retrieve the exit code. In our cause it was being caused by the Amazon Auto Scaling Group trying to rebalance multiple AZs despite active pipelines being executed on the node.\n\n### System Info\n\n```shell\nWoodpecker v2.1.1\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[3091],{"name":3018,"color":3019},3330,"(Kubernetes backend) terminated node causes runtime error when handling step exit code","2024-02-05T21:46:15Z","https://github.com/woodpecker-ci/woodpecker/issues/3330",0.6699359,{"description":3098,"labels":3099,"number":3101,"owner":3021,"repository":3022,"state":3072,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Component\n\nserver\n\n### Describe the bug\n\nI'm having job running issues with woodpecker v0.15.0. Builds stay stuck into queue ; they display as \"not yet started\" in the web interface. According to logs, the server is up and the agent seems able to connect to it. The only log I was able to get is when I try and jump to a pending job in the right panel in the web interface. Then the server complains : \r\n``` json\r\n{\"level\":\"error\",\"error\":\"Error #01: sql: no rows in result set\\n\",\"ip\":\"192.168.1.1\",\"latency\":15.180251,\"method\":\"GET\",\"path\":\"/api/repos/lafleur/wanderings/logs/19/1\",\"status\":404,\"time\":\"2022-04-01T13:34:57Z\",\"user-agent\":\"Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0\",\"time\":\"2022-04-01T13:34:57Z\"}\r\n{\"level\":\"error\",\"error\":\"Error #01: sql: no rows in result set\\n\",\"ip\":\"::1\",\"latency\":14.972052,\"method\":\"GET\",\"path\":\"/api/repos/lafleur/wanderings/logs/19/1\",\"status\":404,\"time\":\"2022-04-01T13:34:57Z\",\"user-agent\":\"Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0\",\"time\":\"2022-04-01T13:34:57Z\"}\r\n```\r\n\r\nI'm running on a barebone ARMv7 Arch system, installing through its [PKGBUILD](https://aur.archlinux.org/packages/woodpecker).\r\n\r\nI tried rolling back to v0.15.0-rc2. The result is the same, although this time the agent seems unable to connect to the server. Logs from the agent :\r\n``` json\r\n{\"level\":\"error\",\"error\":\"rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \\\"error reading from server: EOF\\\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \\\"too_many_pings\\\"\",\"time\":\"2022-04-01T13:47:45Z\",\"message\":\"grpc error: done(): code: Unavailable: rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \\\"error reading from server: EOF\\\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \\\"too_many_pings\\\"\"}\r\n```\r\nMy RC2 version is `next-c79aa2b1`.\r\n\r\nRolling back to [v0.15.0-rc1](https://github.com/woodpecker-ci/woodpecker/releases/tag/v0.15.0-rc1) (version `next-150c5e1c`) does workaround the issue.\r\n\r\nI compared my issue with #841 , and the logs do not match, hence this new issue.\r\n\r\nAny clue appreciated !\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-28b15120\"}\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy).",[3100],{"name":3018,"color":3019},860,"all jobs stall as \"pending\" in queue since v0.15.0_RC2","2022-10-11T16:35:18Z","https://github.com/woodpecker-ci/woodpecker/issues/860",0.672,{"description":3107,"labels":3108,"number":3113,"owner":3021,"repository":3022,"state":3072,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### Component\n\nagent\n\n### Describe the bug\n\nSince I'm on 3.4.0, the agent runs into a segmentation fault on startup.\n\nI just updated from woodpecker 2.7.0 to 3.4.0.\nI'm using [picus](https://github.com/windsource/picus) 0.7.2 to deploy VMs for agents as needed.\nIt does not appear to be a picus issue: https://github.com/windsource/picus/issues/29\n\n### Steps to reproduce\n\n1. Create woodpecker agent with the compose config attached below\n2. Watch it crash\n\nMy woodpecker server has pending jobs for the agent in case that's relevant.\n\n### Expected behavior\n\nno crash\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"3.4.0\"}\n\n\n\nservices:\n\n woodpecker-agent:\n image: woodpeckerci/woodpecker-agent:v3.4.0-alpine\n command: agent\n restart: always\n volumes:\n - /var/run/docker.sock:/var/run/docker.sock\n environment:\n - WOODPECKER_GRPC_SECURE=true\n - WOODPECKER_BACKEND=docker\n - WOODPECKER_SERVER=[...]:443\n - WOODPECKER_FILTER_LABELS=platform=linux/amd64,backend=docker,repo=*,org-id=*\n - WOODPECKER_AGENT_SECRET=[...]\n\n\nWoodpecker runs behind nginx.\n```\n\n### Additional context\n\n```\n2025-03-30T16:28:30.809785618Z {\"level\":\"info\",\"time\":\"2025-03-30T16:28:30Z\",\"message\":\"log level: info\"}\n2025-03-30T16:28:31.036192576Z {\"level\":\"info\",\"time\":\"2025-03-30T16:28:31Z\",\"message\":\"starting Woodpecker agent with version '3.4.0' and backend 'docker' using platform 'linux/amd64' running up to 1 pipelines in parallel\"}\n2025-03-30T16:28:31.676659905Z panic: runtime error: invalid memory address or nil pointer dereference\n2025-03-30T16:28:31.676698591Z \tpanic: runtime error: invalid memory address or nil pointer dereference\n2025-03-30T16:28:31.676703160Z [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xa7745f]\n2025-03-30T16:28:31.676706736Z\n2025-03-30T16:28:31.676710003Z goroutine 66 [running]:\n2025-03-30T16:28:31.676713380Z go.woodpecker-ci.org/woodpecker/v3/pipeline/backend/docker.(*docker).DestroyWorkflow(0x3507160, {0x2381360, 0xc0004656d0}, 0xc0000cc940, {0xc00011952b, 0x3})\n2025-03-30T16:28:31.676717768Z \t/src/pipeline/backend/docker/docker.go:326 +0xff\n2025-03-30T16:28:31.676721617Z go.woodpecker-ci.org/woodpecker/v3/pipeline.(*Runtime).Run.func1()\n2025-03-30T16:28:31.676725223Z \t/src/pipeline/pipeline.go:112 +0x7f\n2025-03-30T16:28:31.676749921Z panic({0x1d283c0?, 0x34ca3c0?})\n2025-03-30T16:28:31.676752406Z \t/usr/local/go/src/runtime/panic.go:792 +0x132\n2025-03-30T16:28:31.676754861Z go.woodpecker-ci.org/woodpecker/v3/pipeline/backend/docker.(*docker).SetupWorkflow(0x3507160, {0x2381360, 0xc0004656d0}, 0xc0000cc940, {0xc00011952b, 0x3})\n2025-03-30T16:28:31.676757557Z \t/src/pipeline/backend/docker/docker.go:148 +0xf5\n2025-03-30T16:28:31.676759992Z go.woodpecker-ci.org/woodpecker/v3/pipeline.(*Runtime).Run(0xc000246af0, {0x2381360, 0xc0004656d0})\n2025-03-30T16:28:31.676762536Z \t/src/pipeline/pipeline.go:118 +0x2eb\n2025-03-30T16:28:31.676764881Z go.woodpecker-ci.org/woodpecker/v3/agent.(*Runner).Run(0xc00002f300, {0x2381360, 0xc0004656d0}, {0x23812f0, 0x3528280})\n2025-03-30T16:28:31.676767556Z \t/src/agent/runner.go:153 +0xeb3\n2025-03-30T16:28:31.676774199Z go.woodpecker-ci.org/woodpecker/v3/cmd/agent/core.run.func5()\n2025-03-30T16:28:31.676776774Z \t/src/cmd/agent/core/agent.go:293 +0x205\n2025-03-30T16:28:31.676779170Z golang.org/x/sync/errgroup.(*Group).Go.func1()\n2025-03-30T16:28:31.676781634Z \t/src/vendor/golang.org/x/sync/errgroup/errgroup.go:78 +0x50\n2025-03-30T16:28:31.676784048Z created by golang.org/x/sync/errgroup.(*Group).Go in goroutine 1\n2025-03-30T16:28:31.676786523Z \t/src/vendor/golang.org/x/sync/errgroup/errgroup.go:75 +0x93\n```\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[3109,3110],{"name":3018,"color":3019},{"name":3111,"color":3112},"agent","ECBCDF",5031,"Segmentation fault on woodpecker-agent startup","2025-07-05T09:59:18Z","https://github.com/woodpecker-ci/woodpecker/issues/5031",0.6729149,["Reactive",3119],{},["Set"],["ShallowReactive",3122],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fsl_xg3o-K0YYKkOTgZZblJ1oRzgphTOjoru4H_B3_Io":-1},"/woodpecker-ci/woodpecker/3712"]