\n\nAnd here is the outcome on BitBucket:\n\u003Cimg width=\"479\" height=\"182\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/11c2a65d-cbf2-4162-9805-3d035bdac04e\" />\n\n\n### Steps to reproduce\n\n1. Run Woodpecker with BitBucket Cloud forge\n2. Create a pipeline that uses a matrix\n3. Let the pipeline finish on Woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\nBoth pipelines should show completed.\n\n### System Info\n\n```shell\nWoodpecker version: v3.8.0\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/versions]",[3039],{"name":3018,"color":3019},5338,"Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.68640554,{"description":3046,"labels":3047,"number":3049,"owner":3021,"repository":3022,"state":3023,"title":3050,"updated_at":3051,"url":3052,"score":3053},"### Component\n\nserver, agent\n\n### Describe the bug\n\nSetup a woordpecker server and agent via 2 docker containers with a shared `WOODPECKER_AGENT_SECRET`\r\nEverything works fine at first, but after a couple of hours the communication between server and agent fails.\r\nThe logs from the agent are:\r\n```\r\n ERR src/agent/rpc/client_grpc.go:461 > grpc error: report_health(): code: Unauthenticated error=\"rpc error: code = Unauthenticated desc = access token is invalid: invalid token: token has invalid claims: token is expired\"\r\n5:40PM ERR src/cmd/agent/core/agent.go:251 > failed to report health error=\"rpc error: code = Unauthenticated desc = access token is invalid: invalid token: token has invalid claims: token is expired\"\r\n```\r\nThe server doesn't log anything relevant about it I think.\r\nSo since this is so basic, I really hesitated to report that bug, believing I made some mistake, so I actually recreated my real setup with the most basic setup just locally and it is the same problem.\n\n### Steps to reproduce\n\n1. start server with:\r\n```\r\ndocker run --rm -it -p 8000:8000 -p 9000:9000 -v ./datatest:/var/lib/woodpecker -e WOODPECKER_HOST=http://localhost:8000 -e WOODPECKER_AGENT_SECRET=ADFI34YAKMIGSNKK55IPCKVVJWNULOBQY2QRIBJ42X527NY7GLTQ===1 -v /var/run/docker.sock:/var/run/docker.sock -e WOODPECKER_LOG_LEVEL=debug -e WOODPECKER_GITEA=true -e WOODPECKER_GITEA_CLIENT=... -e WOODPECKER_GITEA_SECRET=...-e WOODPECKER_GITEA_URL=... -e WOODPECKER_OPEN=true -e WOODPECKER_ADMIN=martin --name woodpecker-server-test woodpeckerci/woodpecker-server:v2.7.1-alpine\r\n```\r\n2. start agent with:\r\n```\r\ndocker run --rm -it --network host -e WOODPECKER_SERVER=localhost:9000 -e WOODPECKER_AGENT_SECRET=ADFI34YAKMIGSNKK55IPCKVVJWNULOBQY2QRIBJ42X527NY7GLTQ===1 -v /var/run/docker.sock:/var/run/docker.sock -e WOODPECKER_LOG_LEVEL=debug --name woodpecker-runner-test woodpeckerci/woodpecker-agent:v2.7.1-alpine\r\n```\r\n3. check it works\r\n4. wait for a day and you will see the error in the agent logs, server doesn't report anything related i think\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n* woodpeckerci/woodpecker-server:v2.7.1-alpine\r\n* woodpeckerci/woodpecker-agent:v2.7.1-alpine\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]",[3048],{"name":3018,"color":3019},4144,"agent connection seems broken, rpc access token expired","2024-10-08T07:04:00Z","https://github.com/woodpecker-ci/woodpecker/issues/4144",0.7065622,{"description":3055,"labels":3056,"number":3058,"owner":3021,"repository":3022,"state":3059,"title":3060,"updated_at":3061,"url":3062,"score":3063},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nThe Woodpecker agent keeps restarting because of a permissions issue with the Docker socket.\r\nAs I have updated about 15 minutes ago I suspect this is caused by #4617.\r\n\r\nMy docker compose config.\r\n```\r\nname: dev_woodpecker-agent\r\n\r\nservices:\r\n woodpecker-agent:\r\n image: woodpeckerci/woodpecker-agent:next\r\n container_name: dev_woodpecker-agent\r\n restart: always\r\n command: agent\r\n networks:\r\n - web\r\n volumes:\r\n - /var/run/docker.sock:/var/run/docker.sock\r\n environment:\r\n - WOODPECKER_SERVER=\u003Cdomain>\r\n - WOODPECKER_GRPC_SECURE=true\r\n - WOODPECKER_AGENT_SECRET=\u003Csecret>\r\n - WOODPECKER_AGENT_BACKEND=docker\r\n - WOODPECKER_FILTER_LABELS=hostname=\u003Chostname>\r\n - WOODPECKER_HOSTNAME=\u003Chostname>\r\n\r\nnetworks:\r\n web:\r\n external: true\r\n```\r\n\r\n### Steps to reproduce\r\n\r\n.\r\n\r\n### Expected behavior\r\n\r\n_No response_\r\n\r\n### System Info\r\n\r\n```shell\r\nWoodpecker version: 20323a8302\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n```\r\n{\"level\":\"error\",\"error\":\"permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get \\\"http://%2Fvar%2Frun%2Fdocker.sock/v1.47/info\\\": dial unix /var/run/docker.sock: connect: permission denied\",\"time\":\"2025-01-08T09:22:29Z\",\"message\":\"cannot load backend engine\"}\r\n{\"level\":\"info\",\"time\":\"2025-01-08T09:22:29Z\",\"message\":\"shutdown of whole agent\"}\r\n{\"level\":\"fatal\",\"error\":\"permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get \\\"http://%2Fvar%2Frun%2Fdocker.sock/v1.47/info\\\": dial unix /var/run/docker.sock: connect: permission denied\",\"time\":\"2025-01-08T09:22:29Z\",\"message\":\"error running agent\"}\r\n{\"level\":\"info\",\"time\":\"2025-01-08T09:22:55Z\",\"message\":\"log level: info\"}\r\n{\"level\":\"error\",\"error\":\"permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get \\\"http://%2Fvar%2Frun%2Fdocker.sock/v1.47/info\\\": dial unix /var/run/docker.sock: connect: permission denied\",\"time\":\"2025-01-08T09:22:55Z\",\"message\":\"cannot load backend engine\"}\r\n{\"level\":\"info\",\"time\":\"2025-01-08T09:22:55Z\",\"message\":\"shutdown of whole agent\"}\r\n{\"level\":\"fatal\",\"error\":\"permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get \\\"http://%2Fvar%2Frun%2Fdocker.sock/v1.47/info\\\": dial unix /var/run/docker.sock: connect: permission denied\",\"time\":\"2025-01-08T09:22:55Z\",\"message\":\"error running agent\"}\r\n{\"level\":\"info\",\"time\":\"2025-01-08T09:23:47Z\",\"message\":\"log level: info\"}\r\n{\"level\":\"error\",\"error\":\"permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get \\\"http://%2Fvar%2Frun%2Fdocker.sock/v1.47/info\\\": dial unix /var/run/docker.sock: connect: permission denied\",\"time\":\"2025-01-08T09:23:47Z\",\"message\":\"cannot load backend engine\"}\r\n{\"level\":\"info\",\"time\":\"2025-01-08T09:23:47Z\",\"message\":\"shutdown of whole agent\"}\r\n{\"level\":\"fatal\",\"error\":\"permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get \\\"http://%2Fvar%2Frun%2Fdocker.sock/v1.47/info\\\": dial unix /var/run/docker.sock: connect: permission denied\",\"time\":\"2025-01-08T09:23:47Z\",\"message\":\"error running agent\"}\r\n{\"level\":\"info\",\"time\":\"2025-01-08T09:24:47Z\",\"message\":\"log level: info\"}\r\n{\"level\":\"error\",\"error\":\"permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get \\\"http://%2Fvar%2Frun%2Fdocker.sock/v1.47/info\\\": dial unix /var/run/docker.sock: connect: permission denied\",\"time\":\"2025-01-08T09:24:47Z\",\"message\":\"cannot load backend engine\"}\r\n{\"level\":\"info\",\"time\":\"2025-01-08T09:24:47Z\",\"message\":\"shutdown of whole agent\"}\r\n{\"level\":\"fatal\",\"error\":\"permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get \\\"http://%2Fvar%2Frun%2Fdocker.sock/v1.47/info\\\": dial unix /var/run/docker.sock: connect: permission denied\",\"time\":\"2025-01-08T09:24:47Z\",\"message\":\"error running agent\"}\r\n```\r\n\r\n### Validations\r\n\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] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[3057],{"name":3018,"color":3019},4681,"closed","Agent keeps restarting due to permission issue.","2025-01-08T20:35:59Z","https://github.com/woodpecker-ci/woodpecker/issues/4681",0.65958595,{"description":3065,"labels":3066,"number":3067,"owner":3021,"repository":3022,"state":3059,"title":3068,"updated_at":3069,"url":3070,"score":3071},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nWoodpecker Agent is being shown as `starting` when executing `docker ps -a` / `podman ps -a`.\r\n\r\n### System Info\r\n\r\n`Artix Linux Rolling - OpenRC`\r\n```\r\nversion\t\"0.15.6\"\r\n```\r\n\r\nOn podman / `podman.sock`.\r\n\r\nRunner:\r\n```\r\n#!/usr/bin/openrc-run\r\n\r\nsupervisor=supervise-daemon\r\n\r\ndepend() {\r\n\tneed localmount net pihole postgresql woodpecker-server pipeline\r\n}\r\n\r\nstart() {\r\n\techo -n \"Starting:\"\r\n\tif [ \"$(podman ps -aq -f name='cwoodpecker')\" ]; then\r\n\t\tpodman stop cwoodpecker > /dev/null\r\n\tfi\r\n\r\n\tif [ \"$(podman ps -aq -f name='cwoodpecker')\" ]; then\r\n\t\tpodman start cwoodpecker\r\n\telse\r\n\t\tpodman run \\\r\n\t\t\t-d --restart=unless-stopped \\\r\n\t\t\t--stop-signal SIGKILL \\\r\n\t\t\t--name cwoodpecker \\\r\n\t\t\t--ip 192.168.2.13 \\\r\n\t\t\t--privileged \\\r\n\t\t\t-v /server/pipeline:/listen \\\r\n\t\t\t-e WOODPECKER_LOG_LEVEL=warn \\\r\n\t\t\t-e WOODPECKER_HOSTNAME=woodpeckeragent \\\r\n\t\t\t-e WOODPECKER_AGENT_SECRET=\"secret\" \\\r\n\t\t\t-e WOODPECKER_HEALTHCHECK=false \\\r\n\t\t\t-e WOODPECKER_MAX_PROCS=2 \\\r\n\t\t\t-e WOODPECKER_SERVER=192.168.2.14:9000 \\\r\n\t\t\t-e WOODPECKER_BACKEND=docker \\\r\n\t\t\t-e DOCKER_HOST=\"unix:///listen/podman.sock\" \\\r\n\t\t\twoodpeckerci/woodpecker-agent\r\n\tfi\r\n}\r\n\r\nstop() {\r\n\tif [ \"$(podman ps -aq -f name='cwoodpecker')\" ]; then\r\n\t\tpodman stop cwoodpecker > /dev/null\r\n\tfi\r\n}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\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] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\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).",[],1624,"Woodpecker Agent is being shown as `starting` in a container.","2023-08-21T15:18:39Z","https://github.com/woodpecker-ci/woodpecker/issues/1624",0.66020125,{"description":3073,"labels":3074,"number":3079,"owner":3021,"repository":3022,"state":3059,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Component\n\nweb-ui\n\n### Describe the bug\n\nI am attempting to use Woodpecker to build an image using the [Cypress Factory](https://hub.docker.com/r/cypress/factory/) docker image that can be used with docker args to generate a container with specific package versions. I am using the woodpecker docker buildx plugin to build the image.\r\n\r\nWhen I run my build job and view the progress in the UI it appears the job is stuck installing GPG keys. However, when I look at the log output on the agent I can see that the GPG key installations are successful and the rest of the job steps are executed and the final image is published.\r\n\r\nAdditionally, the UI never marks the job as completed and the kubernetes builds pods stayed in a 'Completed' state until the job times out or is manually cancelled. When this happens the agents no longer pull new work from the server.\n\n### Steps to reproduce\n\n1. Create a Dockerfile using the Cypress factory image\r\n```\r\nARG NODE_VERSION='18.16.0'\r\nARG YARN_VERSION='1.22.19'\r\nARG CYPRESS_VERSION='13.7.1'\r\nARG CHROME_VERSION='120.0.6099.71-1'\r\nARG EDGE_VERSION='120.0.2210.61-1'\r\nARG FIREFOX_VERSION='120.0.1'\r\n\r\nFROM cypress/factory\r\n```\r\n2. Create a woodpecker job to build the image\r\n```\r\nsteps:\r\n - name: docker-cypress\r\n image: woodpeckerci/plugin-docker-buildx\r\n secrets: [docker_username, docker_password]\r\n settings:\r\n platforms: linux/amd64\r\n registry: \u003Cmy_docker_registry>\r\n repo: \u003Cmy_docker_repo>\r\n dockerfile: Dockerfile.cypress.test\r\n tags: buildx.test-build\r\n username:\r\n from_secret: docker_username\r\n password:\r\n from_secret: docker_password\r\n build_args_from_env:\r\n - CI_REPO\r\n - CI_COMMIT_BRANCH\r\n - CI_COMMIT_SHA\r\n - CI_PIPELINE_NUMBER\r\n debug: true\r\n```\r\n3. Run the job\r\n\n\n### Expected behavior\n\n* The job should successfully build the container and be marked Successful\r\n* The UI log output should stay in sync with the worker agent log output\r\n* The UI should not hang indefinitely during the build\n\n### System Info\n\n```shell\n{\r\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n\"version\": \"2.4.1\"\r\n}\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]",[3075,3076],{"name":3018,"color":3019},{"name":3077,"color":3078},"ui","46DEA2",3716,"Woodpecker UI output not updating/out of sync","2024-06-13T15:18:35Z","https://github.com/woodpecker-ci/woodpecker/issues/3716",0.6674356,{"description":3085,"labels":3086,"number":3088,"owner":3021,"repository":3022,"state":3059,"title":3089,"updated_at":3090,"url":3091,"score":3092},"### Component\n\nagent\n\n### Describe the bug\n\nI'm getting an error on trying to start my Woodpecker CI service using the docker deployment method. The server container starts up fine, but the agent container won't start up because of a authid not being in the database I'm using for it. I have already added my secret to the environment file, but it doesn't notice it at all. My log below shows what I'm talking about. Someone help me out!\n\n### Steps to reproduce\n\nCannot reproduce this issue!\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nCannot get the version and other information!\n```\n\n### Additional context\n\nLog output:\n```\nwoodpecker-server-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:14Z\",\"message\":\"log level: info\"}\nwoodpecker-server-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:14Z\",\"message\":\"starting Woodpecker server with version '2.8.3'\"}\nwoodpecker-server-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:14Z\",\"message\":\"store metric collector started\"}\nwoodpecker-server-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:14Z\",\"message\":\"queue metric collector started\"}\nwoodpecker-server-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:14Z\",\"message\":\"starting cron service ...\"}\nwoodpecker-server-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:14Z\",\"message\":\"starting grpc server ...\"}\nwoodpecker-server-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:14Z\",\"message\":\"starting http server ...\"}\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:14Z\",\"message\":\"log level: info\"}\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:15Z\",\"message\":\"shutdown of whole agent\"}\nwoodpecker-agent-1 | {\"level\":\"fatal\",\"error\":\"rpc error: code = Unknown desc = agent could not auth: AgentID not found in database\",\"time\":\"2025-02-08T02:48:15Z\",\"message\":\"error running agent\"}\nwoodpecker-agent-1 exited with code 0\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:16Z\",\"message\":\"log level: info\"}\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:16Z\",\"message\":\"shutdown of whole agent\"}\nwoodpecker-agent-1 | {\"level\":\"fatal\",\"error\":\"rpc error: code = Unknown desc = agent could not auth: AgentID not found in database\",\"time\":\"2025-02-08T02:48:16Z\",\"message\":\"error running agent\"}\nwoodpecker-agent-1 exited with code 0\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:17Z\",\"message\":\"log level: info\"}\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:17Z\",\"message\":\"shutdown of whole agent\"}\nwoodpecker-agent-1 | {\"level\":\"fatal\",\"error\":\"rpc error: code = Unknown desc = agent could not auth: AgentID not found in database\",\"time\":\"2025-02-08T02:48:17Z\",\"message\":\"error running agent\"}\nwoodpecker-agent-1 exited with code 1\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:18Z\",\"message\":\"log level: info\"}\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:18Z\",\"message\":\"shutdown of whole agent\"}\nwoodpecker-agent-1 | {\"level\":\"fatal\",\"error\":\"rpc error: code = Unknown desc = agent could not auth: AgentID not found in database\",\"time\":\"2025-02-08T02:48:18Z\",\"message\":\"error running agent\"}\nwoodpecker-agent-1 exited with code 1\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:19Z\",\"message\":\"log level: info\"}\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:19Z\",\"message\":\"shutdown of whole agent\"}\nwoodpecker-agent-1 | {\"level\":\"fatal\",\"error\":\"rpc error: code = Unknown desc = agent could not auth: AgentID not found in database\",\"time\":\"2025-02-08T02:48:19Z\",\"message\":\"error running agent\"}\nwoodpecker-agent-1 exited with code 1\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:22Z\",\"message\":\"log level: info\"}\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:22Z\",\"message\":\"shutdown of whole agent\"}\nwoodpecker-agent-1 | {\"level\":\"fatal\",\"error\":\"rpc error: code = Unknown desc = agent could not auth: AgentID not found in database\",\"time\":\"2025-02-08T02:48:22Z\",\"message\":\"error running agent\"}\nwoodpecker-agent-1 exited with code 1\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:26Z\",\"message\":\"log level: info\"}\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:26Z\",\"message\":\"shutdown of whole agent\"}\nwoodpecker-agent-1 | {\"level\":\"fatal\",\"error\":\"rpc error: code = Unknown desc = agent could not auth: AgentID not found in database\",\"time\":\"2025-02-08T02:48:26Z\",\"message\":\"error running agent\"}\nwoodpecker-agent-1 exited with code 1\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:33Z\",\"message\":\"log level: info\"}\nwoodpecker-agent-1 | {\"level\":\"info\",\"time\":\"2025-02-08T02:48:33Z\",\"message\":\"shutdown of whole agent\"}\nwoodpecker-agent-1 | {\"level\":\"fatal\",\"error\":\"rpc error: code = Unknown desc = agent could not auth: AgentID not found in database\",\"time\":\"2025-02-08T02:48:33Z\",\"message\":\"error running agent\"}\nwoodpecker-agent-1 exited with code 1\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]",[3087],{"name":3018,"color":3019},4824,"Agent container refuses to start up","2025-02-10T02:20:54Z","https://github.com/woodpecker-ci/woodpecker/issues/4824",0.6800907,{"description":3094,"labels":3095,"number":3100,"owner":3021,"repository":3022,"state":3059,"title":3101,"updated_at":3102,"url":3103,"score":3104},"### 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]",[3096,3097],{"name":3018,"color":3019},{"name":3098,"color":3099},"agent","ECBCDF",5031,"Segmentation fault on woodpecker-agent startup","2025-07-05T09:59:18Z","https://github.com/woodpecker-ci/woodpecker/issues/5031",0.68657935,{"description":3106,"labels":3107,"number":3108,"owner":3021,"repository":3022,"state":3059,"title":3109,"updated_at":3110,"url":3111,"score":3112},"I will give up Woodpecker and return to Drone. reason\n1: GitHub issue #5262 with Woodpecker ui, switching log viewing will cause interruption and result in server shutdown in the background\n2: Plugin https://codeberg.org/woodpecker-plugins/docker-buildx/issues/268 I have been trying to mount the host volume but have not received a response\nBecause these two issues affect normal use and there has been no feedback from the management for a week, I have to give up",[],5276,"Giveup","2025-07-17T08:18:51Z","https://github.com/woodpecker-ci/woodpecker/issues/5276",0.689577,["Reactive",3114],{},["Set"],["ShallowReactive",3117],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fusG4ebpkQaVYuAZ_c0j7a3h0BT57RRqHRqHMS78pThM":-1},"/woodpecker-ci/woodpecker/178"]