\n\n### Expected behavior\n\n```\ndocker run --rm --privileged \\\n -v $(pwd):/woodpecker \\\n -e PLUGIN_REPO=demo/myap \\\n -e PLUGIN_TAGS=latest \\\n -e PLUGIN_PLATFORMS=linux/amd64 \\\n -e PLUGIN_DOCKERFILE=Dockerfile \\\n -e PLUGIN_DRIVER=docker \\\n -e PLUGIN_BUILDKIT_DRIVEROPT=\"image=moby/buildkit:master\" \\\n -w /woodpecker \\\n woodpeckerci/plugin-docker-buildx:5.2.2-insecure\n```\n\n\u003Cimg width=\"2083\" height=\"456\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/763aa4cd-edc1-4e07-b043-44b5d153d962\" />\n\n### System Info\n\n```shell\ndocker desktop v4.43.1\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]",[3065],{"name":3018,"color":3019},5321,"plugin-docker-buildx insecure with PLUGIN_BUILDKIT_DRIVEROPT image not work after version 6","2025-07-22T14:24:24Z","https://github.com/woodpecker-ci/woodpecker/issues/5321",0.6695679,{"description":3072,"labels":3073,"number":3075,"owner":3021,"repository":3022,"state":3036,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### 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]",[3074],{"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.66961,{"description":3081,"labels":3082,"number":3087,"owner":3021,"repository":3022,"state":3036,"title":3088,"updated_at":3089,"url":3090,"score":3091},"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```",[3083,3084],{"name":3018,"color":3019},{"name":3085,"color":3086},"server","5D7A92",232,"Latest image doesn't run ?","2021-06-30T15:17:55Z","https://github.com/woodpecker-ci/woodpecker/issues/232",0.6697145,{"description":3093,"labels":3094,"number":3096,"owner":3021,"repository":3022,"state":3036,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### Component\n\nweb-ui\n\n### Describe the bug\n\nThe pipeline status image (on Woodpecker - returned by API: /api/badges/25/status.svg ) shows ERROR, even that last build is OK:\r\n\r\n\n\n### System Info\n\n```shell\nversion 2.4.1 running on Docker\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]",[3095],{"name":3018,"color":3019},3561,"Pipeline status is error, but last job is OK","2024-04-15T10:15:05Z","https://github.com/woodpecker-ci/woodpecker/issues/3561",0.6719708,{"description":3102,"labels":3103,"number":3105,"owner":3021,"repository":3022,"state":3036,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Component\n\nserver\n\n### Describe the bug\n\n\r\n\r\nI'll try to downgrade my woodpecker version to fix this, because all PRs are now broken on `next`.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-5bd12aa646\"}\n```\n\n\n### Additional context\n\nNA\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/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] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\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).",[3104],{"name":3018,"color":3019},2350,"All github PRs are reported as *Waiting for status to be reported*","2023-10-02T06:45:33Z","https://github.com/woodpecker-ci/woodpecker/issues/2350",0.6733849,{"description":3111,"labels":3112,"number":3114,"owner":3021,"repository":3022,"state":3036,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### Component\n\nserver\n\n### Describe the bug\n\nIn woodpecker v2.3.0, custom yaml files defined in repositories are configured in woodpecker and passed to the external configuration API. This API responds with valid woodpecker workflows based on the custom yaml, allowing this workflow to execute successfully. However, woodpecker 2.4.1 introduces linting on these configured custom yaml files, resulting in failed executions due to linting errors. This change effectively inhibits our ability to upgrade our instance to v2.4.1.\n\n### System Info\n\n```shell\nVersion which works for us\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.3.0\"}\r\n---\r\nVersion with issue\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.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]",[3113],{"name":3018,"color":3019},3536,"Linter errors on repos dependent on external configuration API ","2024-03-22T14:16:02Z","https://github.com/woodpecker-ci/woodpecker/issues/3536",0.68226385,["Reactive",3120],{},["Set"],["ShallowReactive",3123],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fzPvd08mqPD9s8jmENUmMJ_XX9xUBwIx33h5VCEoLQs0":-1},"/woodpecker-ci/woodpecker/4597"]