\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]",[3042],{"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.7213066,{"description":3049,"labels":3050,"number":3055,"owner":3021,"repository":3022,"state":3056,"title":3057,"updated_at":3058,"url":3059,"score":3060},"Hi,\r\n\r\nI just updated my woodpecker docker image (docker pull). It doesn't run.\r\nLast update was when OAuth was added (10 days ago).\r\n\r\n```\r\ntime=\"2021-06-28T16:48:40Z\" level=error msg=\"sql: unknown driver \\\"sqlite3\\\" (forgotten import?)\"\r\ntime=\"2021-06-28T16:48:40Z\" level=fatal msg=\"database connection failed\"\r\n```",[3051,3052],{"name":3018,"color":3019},{"name":3053,"color":3054},"server","5D7A92",232,"closed","Latest image doesn't run ?","2021-06-30T15:17:55Z","https://github.com/woodpecker-ci/woodpecker/issues/232",0.65964323,{"description":3062,"labels":3063,"number":3065,"owner":3021,"repository":3022,"state":3056,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Component\n\nserver\n\n### Describe the bug\n\nwoodpecker server docker image will not start after pulling latest\r\nshowing erro\r\n```\r\n2024-11-06T18:53:01Z INF log level: info \r\n\r\n2024-11-06T18:53:01Z ERR migration step 'create-table-users' missing, please upgrade to last stable v0.14.x version first \r\n\r\n2024-11-06T18:53:01Z ERR error running server | error=can't setup store: could not migrate datastore: migration xorm failed: legacy migration step missing\r\n```\n\n### Steps to reproduce\n\nupdate woodpecker server docker from previou 2.7.2 release\n\n### Expected behavior\n\nserver should start\n\n### System Info\n\n```shell\nv2.7.3\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]",[3064],{"name":3018,"color":3019},4333,"woodpecker server docker image will not start after pulling latest","2024-11-06T20:30:16Z","https://github.com/woodpecker-ci/woodpecker/issues/4333",0.6688451,{"description":3071,"labels":3072,"number":3074,"owner":3021,"repository":3022,"state":3056,"title":3075,"updated_at":3076,"url":3077,"score":3078},"### 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]",[3073],{"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.6809296,{"description":3080,"labels":3081,"number":3083,"owner":3021,"repository":3022,"state":3056,"title":3084,"updated_at":3085,"url":3086,"score":3087},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nI tried updating my docker-compose setup to the latest version, but the server didn't came up. The only logs I got (using `--log-level=trace`) is this:\r\n\r\n```\r\nwoodpecker_1 | {\"time\":\"2021-11-21T16:24:16Z\",\"message\":\"LogLevel = trace\"}\r\nwoodpecker_1 | {\"level\":\"trace\",\"time\":\"2021-11-21T16:24:16Z\",\"message\":\"Remote (gitea) opts: gitea.Opts{URL:\\\"https://git.sp-codes.de\\\", Context:\\\"continuous-integration/woodpecker\\\", Client:\\\"...\\\", Secret:\\\"...\\\", Username:\\\"\\\", Password:\\\"\\\", PrivateMode:false, SkipVerify:false}\"}\r\nwoodpecker_1 | {\"level\":\"trace\",\"time\":\"2021-11-21T16:24:16Z\",\"message\":\"setup datastore: store.Opts{Driver:\\\"postgres\\\", Config:\\\"postgres://...:...@database/woodpecker?sslmode=disable\\\"}\"}\r\nwoodpecker_1 | {\"level\":\"trace\",\"time\":\"2021-11-21T16:24:16Z\",\"message\":\"start migration task 'xorm'\"}\r\nwoodpecker_1 | {\"level\":\"info\",\"time\":\"2021-11-21T16:24:17Z\",\"message\":\"migration task 'xorm' done\"}\r\nwoodpecker_1 | {\"level\":\"trace\",\"time\":\"2021-11-21T16:24:17Z\",\"message\":\"start migration task 'alter-table-drop-repo-fallback'\"}\r\nwoodpecker_1 | {\"level\":\"trace\",\"time\":\"2021-11-21T16:24:17Z\",\"message\":\"migration task 'alter-table-drop-repo-fallback' exist\"}\r\nwoodpecker_1 | {\"level\":\"trace\",\"time\":\"2021-11-21T16:24:17Z\",\"message\":\"start migration task 'drop-allow-push-tags-deploys-columns'\"}\r\nwoodpecker_1 | {\"level\":\"trace\",\"time\":\"2021-11-21T16:24:17Z\",\"message\":\"migration task 'drop-allow-push-tags-deploys-columns' exist\"}\r\nwoodpecker_1 | [xorm] [warn] 2021/11/21 16:24:17.102343 Table agents column agent_id db type is SERIAL, struct type is BIGSERIAL\r\nwoodpecker_1 | [xorm] [warn] 2021/11/21 16:24:17.102375 Table agents column agent_capacity db type is INTEGER, struct type is BIGINT\r\nwoodpecker_1 | [xorm] [warn] 2021/11/21 16:24:17.102379 Table agents column agent_created db type is INTEGER, struct type is BIGINT\r\nwoodpecker_1 | [xorm] [warn] 2021/11/21 16:24:17.102383 Table agents column agent_updated db type is INTEGER, struct type is BIGINT\r\n```\r\n\r\n### System Info\r\n\r\n```shell\r\nNot available, because the server didn't start.\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] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy).",[3082],{"name":3018,"color":3019},518,"Latest Docker Image does not work","2021-11-27T11:02:53Z","https://github.com/woodpecker-ci/woodpecker/issues/518",0.68313783,{"description":3089,"labels":3090,"number":3092,"owner":3021,"repository":3022,"state":3056,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nSetting WOODPECKER_DATABASE_DRIVER=postgres and WOODPECKER_DATABASE_DATASOURCE=postgress://user:pass@domain, according to https://woodpecker-ci.org/docs/administration/database#configure-postgres, starts using sqlite and will open a file at WOODPECKER_DATABASE_DATASOURCE, which is a postgres URI.\r\n\r\nAlso the link to the FAQ is broken: https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use\r\n\r\n### Steps to reproduce\r\n\r\n1. Install using helm chart\r\n2. Set WOODPECKER_DATABASE_DRIVER and WOODPECKER_DATABASE_DATASOURCE\r\n\r\nObserve:\r\n```\r\n+ woodpecker-server-0 › server\r\nwoodpecker-server-0 server {\"level\":\"info\",\"time\":\"2024-08-11T10:19:43Z\",\"message\":\"log level: info\"}\r\nwoodpecker-server-0 server {\"level\":\"warn\",\"time\":\"2024-08-11T10:19:43Z\",\"message\":\"no sqlite3 file found, will create one at 'postgress://user:pass@domain'\"}\r\nwoodpecker-server-0 server {\"level\":\"fatal\",\"error\":\"can't setup store: could not migrate datastore: unable to open database file: no such file or directory\",\"time\":\"2024-08-11T10:19:43Z\",\"message\":\"error running server\"}\r\n- woodpecker-server-0 › server\r\n```\r\n\r\n### Expected behavior\r\n\r\nNo sqlite creation as a valid postgres DB is provided.\r\n\r\n### System Info\r\n\r\n```shell\r\nCant really provide, as the server wont start.\r\n\r\nChart Version: 1.5.1\r\nApp Version: woodpeckerci/woodpecker-agent:v2.7.0\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 [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]",[3091],{"name":3018,"color":3019},4026,"Setting WOODPECKER_DATABASE_DRIVER and WOODPECKER_DATABASE_DATASOURCE starts using sqlite","2024-08-11T10:28:57Z","https://github.com/woodpecker-ci/woodpecker/issues/4026",0.6880135,{"description":3098,"labels":3099,"number":3104,"owner":3021,"repository":3022,"state":3056,"title":3105,"updated_at":3106,"url":3107,"score":3108},"### 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]",[3100,3101],{"name":3018,"color":3019},{"name":3102,"color":3103},"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.70752805,{"description":3110,"labels":3111,"number":3113,"owner":3021,"repository":3022,"state":3056,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### Component\n\nserver\n\n### Describe the bug\n\nAfter #4597, I switched from `latest` to `v3.0.0-rc1` as suggested. That was the only version that would allow `docker compose` to run correctly.\n\nTrying to move to any other version (preferably `v3.0.1` which is the latest as of the creation of the issue), the server container fails to start with this error:\n```\nwoodpecker-server-1 | 4:44PM ERR error running server error=\"can't setup store: could not migrate datastore: migration remove-repo-scm failed: attempt to write a readonly database\"\n```\nSubsequently, the agent fails:\n```\nwoodpecker-agent-1-1 | 4:44PM ERR cannot listen on address :3000 error=\"http: Server closed\"\n```\n\nUnfortunately, I lack the knowledge to debug this further, but I'm open to suggestions.\n\n### Steps to reproduce\n\n1. Using a `docker-compose.yaml` with `latest` tags, launch a server/agent configuration (this was consistently used with restarts)\n2. At the removal of `latest` restarting docker compose, the version showed a gPRC error, and a manual switch was done to `v3.0.0-rc1`\n3. Updating to `v3.0.1` throws this error (for the server): `woodpecker-server-1 | 4:44PM ERR error running server error=\"can't setup store: could not migrate datastore: migration remove-repo-scm failed: attempt to write a readonly database\"`\n\n### Expected behavior\n\nUpdating versions should not throw any errors, I believe, as was the case up to the description mentioned above.\n\n### System Info\n\n```shell\n{\n \"source\": \"https://github.com/woodpecker-ci/woodpecker\",\n \"version\": \"3.0.0-rc1\"\n}\n\nRunning on `DISTRIB_DESCRIPTION=\"Ubuntu 24.04.1 LTS\"`\n```\n\n### Additional context\n\nLogs:\n```terminal\n○ → docker compose up\n[+] Running 9/9\n ✔ woodpecker-agent-1 Pulled 5.4s\n ✔ d601d9c28929 Pull complete 2.9s\n ✔ 4f4fb700ef54 Pull complete 3.2s\n ✔ woodpecker-server Pulled 5.2s\n ✔ d7a2fb7ddea2 Pull complete 0.5s\n ✔ b49e16775238 Pull complete 1.8s\n ✔ aea14e118adc Pull complete 3.4s\n ✔ c1190b01ae4f Pull complete 3.4s\n ✔ 5ebc015c6058 Pull complete 3.2s\n[+] Running 3/3\n ✔ Network root_default Created 0.3s\n ✔ Container root-woodpecker-server-1 Created 1.0s\n ✔ Container root-woodpecker-agent-1-1 Created 0.2s\nAttaching to woodpecker-agent-1-1, woodpecker-server-1\nwoodpecker-server-1 | 4:44PM INF log level: info\nwoodpecker-server-1 | 4:44PM ERR error running server error=\"can't setup store: could not migrate datastore: migration remove-repo-scm failed: attempt to write a readonly database\"\nwoodpecker-server-1 exited with code 0\nwoodpecker-agent-1-1 | 4:44PM INF log level: info\nwoodpecker-agent-1-1 | 4:44PM INF no agent config found at '/etc/woodpecker/agent.conf', start with defaults\nwoodpecker-agent-1-1 | 4:44PM INF shutdown of whole agent\nwoodpecker-agent-1-1 | 4:44PM WRN cannot connect to server, retrying in 2s error=\"could not create new auth interceptor: rpc error: code = Unavailable desc = dns: A record lookup error: lookup woodpecker-server on 127.0.0.11:53: server misbehaving\"\nwoodpecker-agent-1-1 | 4:44PM INF shutdown healthcheck server ...\nwoodpecker-agent-1-1 | 4:44PM ERR cannot listen on address :3000 error=\"http: Server closed\"\nwoodpecker-agent-1-1 | 4:44PM INF healthcheck server stopped\nwoodpecker-agent-1-1 | 4:44PM INF no agent config found at '/etc/woodpecker/agent.conf', start with defaults\nwoodpecker-agent-1-1 | 4:44PM INF shutdown of whole agent\nwoodpecker-agent-1-1 | 4:44PM WRN cannot connect to server, retrying in 2s error=\"could not create new auth interceptor: rpc error: code = Unavailable desc = dns: A record lookup error: lookup woodpecker-server on 127.0.0.11:53: server misbehaving\"\nwoodpecker-agent-1-1 | 4:44PM INF shutdown healthcheck server ...\nwoodpecker-agent-1-1 | 4:44PM ERR cannot listen on address :3000 error=\"http: Server closed\"\nwoodpecker-agent-1-1 | 4:44PM INF healthcheck server stopped\n^CGracefully stopping... (press Ctrl+C again to force)\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/faq#which-version-of-woodpecker-should-i-use]",[3112],{"name":3018,"color":3019},4760,"Cannot use versions past v3.0.0-rc1 due to migration failure","2025-01-26T19:22:27Z","https://github.com/woodpecker-ci/woodpecker/issues/4760",0.7095287,["Reactive",3119],{},["Set"],["ShallowReactive",3122],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRsT2sJ5oCaNa7F_eHcLECRXbKvmPTXDANSuuHgq6kn0":-1},"/woodpecker-ci/woodpecker/4955"]