\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]",[3201],{"name":3178,"color":3179},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.7031829,{"description":3208,"labels":3209,"number":3211,"owner":3158,"repository":3159,"state":3184,"title":3212,"updated_at":3213,"url":3214,"score":3215},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nWith the `2.7.1` -> `2.7.2` upgrade, woodpecker always returns a blank page. It seems to be trying to redirect to the `/login?url=/repos` page, but returns a blank page\r\n\r\n### Steps to reproduce\r\n\r\n1. Have a working 2.7.1 install\r\n2. Upgrade to 2.7.2\r\n3. All pages are blank, and the loging redirect fails.\r\n\r\n### Expected behavior\r\n\r\nIt should correctly handle login redirects\r\n\r\n### System Info\r\n\r\n```shell\r\n`\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.7.2\"}`\r\n```\r\n\r\nLuckily there were no migrations as far as I can tell, so switching back to the `v2.7.1` docker tag seems to be working fine.\r\n\r\n### Additional context\r\n\r\nNA\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]",[3210],{"name":3178,"color":3179},4294,"Woodpecker `2.7.2` broke login auth redirects, always returns blank page.","2024-11-06T17:32:33Z","https://github.com/woodpecker-ci/woodpecker/issues/4294",0.7038816,{"description":3217,"labels":3218,"number":3220,"owner":3158,"repository":3159,"state":3184,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### Component\n\nserver\n\n### Describe the bug\n\nI cant login, getting a \"internal error\" on the login screen and this message in the logs\r\n\r\n`{\"level\":\"error\",\"error\":\"sql: no rows in result set\",\"time\":\"2024-09-05T10:36:31Z\",\"message\":\"cannot get org s00500\"}`\n\n### Steps to reproduce\n\nRunning in Kubernetes, using github\n\n### Expected behavior\n\nBe able to log in\n\n### System Info\n\n```shell\n2.7.0 release\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]",[3219],{"name":3178,"color":3179},4086,"Stuck on Login (Github)","2024-09-17T16:57:22Z","https://github.com/woodpecker-ci/woodpecker/issues/4086",0.7142735,{"description":3226,"labels":3227,"number":3229,"owner":3158,"repository":3159,"state":3184,"title":3230,"updated_at":3231,"url":3232,"score":3233},"### Component\n\nagent\n\n### Describe the bug\n\n### The bug\r\n\r\nI want to build and push an OCI image (aka docker image) on my self-hosted registry. I'm running Woodpecker with Kubernetes backend.\r\n\r\nI have this error : `x509: certificate signed by unknown authority`.\r\n\r\n### Explanation\r\n\r\nThe `docker build` is not aware of my `ca.crt` file.\r\n\r\n### How to fix the bug\r\n\r\n1. Find a way to provide my `ca.crt` to the agent (easy to do, need a little hack of the helm chart)\r\n2. Find a way for the agent to provide that `ca.crt` to plugins like _plugin-docker-buildx_ (like `WOODPECKER_BACKEND_DOCKER_VOLUMES` but that does not work with Kubernetes backend)\r\n\r\n### What I did, what I tried...\r\n\r\nI have read a lot of documentation on how to build+push my image. I have also read some parts of source code of Woodpecker Kubernetes backend. I have hacked the helm chart in order to put my ca.crt in a ConfigMap and mount it (with success) in either the agent pod or the dind pod (I will probably do a PR for this in repo woodpecker-ci/helm). \r\n\r\nI have tried with `WOODPECKER_BACKEND_DOCKER_VOLUMES` variable but this is restricted to Docker backend. I found nothing similar for Kubernetes.\r\n\r\nAt last, it does not work whatever I do.\r\n\r\nMy favorite try (with and without dind enabled) :\r\n```\r\n publish-woodpecker-branch:\r\n image: woodpeckerci/plugin-docker-buildx\r\n settings:\r\n registry: myregistry:5001\r\n logins:\r\n - registry: https://myregistry:5001/v2\r\n repo: myregistry:5001/awesome/tool\r\n platforms: linux/arm64\r\n tags:\r\n - ${CI_COMMIT_TAG=build}-${CI_COMMIT_SHA:0:8}-arm64\r\n```\r\n\r\nThis should work but I fail at mounting the ConfigMap in the plugin-docker-buildx pod.\r\n\r\nAnother try (too complex I guess):\r\n\r\n```\r\n publish-woodpecker-branch:\r\n image: docker:20.10.12-dind\r\n secrets:\r\n - registry_ca_crt\r\n commands:\r\n - mkdir -p \"/etc/docker/myregistry:5001\"\r\n - echo \"$${REGISTRY_CA_CRT}\" > \"/etc/docker/myregistry:5001/ca.crt\"\r\n - docker build -t \"myregistry:5001/awesome/tool:$${CI_COMMIT_TAG=build}-$${CI_COMMIT_SHA:0:8}-arm64\" .\r\n - docker push \"myregistry:5001/awesome/tool:$${CI_COMMIT_TAG=build}-$${CI_COMMIT_SHA:0:8}-arm64\"\r\n volumes:\r\n - /var/run/docker.sock:/var/run/docker.sock\r\n```\r\n\r\nI get this error : `Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?`\r\n\r\nI have also tried with Podman but I'm getting problems to run in privileged mode.\r\n\n\n### System Info\n\n```shell\n### Version\r\n\r\n\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-3033abc3\"}\r\n```\r\n\r\n### Helm values\r\n\r\nNotice the hack with `extraVolumes` and `extraVolumeMounts`. `registry-ca-crt` is a ConfigMap that contains a key named `ca.crt` and the value is the CA certificate.\r\n\r\n```\r\n---\r\nserver:\r\n image:\r\n tag: next-3033abc3b4\r\n env:\r\n WOODPECKER_ADMIN: \"\u003Credacted>\"\r\n WOODPECKER_HOST: \"http://woodpecker.\u003Credacted>\"\r\n WOODPECKER_GITEA_URL: \"http://gitea.\u003Credacted>\"\r\n WOODPECKER_GITEA: \"true\"\r\n WOODPECKER_GITEA_SKIP_VERIFY: \"true\"\r\n WOODPECKER_OPEN: \"true\"\r\n WOODPECKER_ORGS: \"\u003Credacted>\"\r\n\r\n extraSecretNamesForEnvFrom:\r\n - woodpecker-gitea-client\r\n - woodpecker-gitea-secret\r\n - woodpecker-secret\r\n\r\n fullnameOverride: \"woodpecker\"\r\n\r\n persistentVolume:\r\n enabled: true\r\n size: 10Gi\r\n storageClass: \"\u003Credacted>\"\r\n\r\nagent:\r\n image:\r\n tag: next-3033abc3b4\r\n env:\r\n WOODPECKER_SERVER: \"woodpecker.woodpecker.svc.cluster.local:9000\"\r\n WOODPECKER_BACKEND: \"kubernetes\"\r\n WOODPECKER_BACKEND_K8S_STORAGE_CLASS: \"\u003Credacted (same as above)>\"\r\n# WOODPECKER_BACKEND_DOCKER_VOLUMES: \"/etc/docker/certs.d:/etc/docker/certs.d:ro\"\r\n\r\n extraSecretNamesForEnvFrom:\r\n - woodpecker-secret\r\n\r\n extraVolumes:\r\n - name: registry-ca-crt\r\n configMap:\r\n name: registry-ca-crt\r\n\r\n# dind:\r\n# enabled: true\r\n# extraVolumeMounts:\r\n# - name: registry-ca-crt\r\n# mountPath: \"/etc/docker/certs.d/myregistry:5001\"\r\n\r\n fullnameOverride: \"woodpecker-agent\"\r\n```\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] 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).",[3228],{"name":3178,"color":3179},1918,"x509: certificate signed by unknown authority (cannot provide ca.crt)","2023-07-22T10:17:32Z","https://github.com/woodpecker-ci/woodpecker/issues/1918",0.7176203,{"description":3235,"labels":3236,"number":3240,"owner":3158,"repository":3159,"state":3184,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nI have set up the Woodpecker server and agent using the Docker Compose configuration shown below. When I first went to the Woodpecker UI at https://ci.example.com and tapped on the **Login** button, I saw the OAuth2 confirmation page on Gitea and tapped the button to allow Woodpecker access. Indeed, I see that Woodpecker is listed under the _Authorized OAuth2 Applications_ heading in the Gitea settings, so it seems that step completed successfully.\r\n\r\nHowever, the login process in the browser seemed to take a long time, eventually showing an error: _\"Error while authenticating against OAuth provider\"_\r\n\r\nRepeated login attempts always result in the same delay and ultimate error. See below for the corresponding error in the Docker Compose log. It is possible that this is related to a networking issue of some kind, but try as I might I cannot figure out how to resolve the problem.\r\n\r\n### System Info\r\n\r\nWoodpecker version: 0.15.0\r\n\r\n\u003Cdetails>\r\n \u003Csummary>Docker Compose configuration (tap here to expand)\u003C/summary>\r\n\r\n```yaml\r\nversion: \"3\"\r\n\r\nservices:\r\n traefik:\r\n image: traefik:v2.6\r\n container_name: traefik\r\n restart: unless-stopped\r\n labels:\r\n - \"traefik.enable=true\"\r\n - \"traefik.http.routers.api.rule=Host(`traefik.example.com`)\"\r\n - \"traefik.http.routers.api.entrypoints=https\"\r\n - \"traefik.http.routers.api.service=api@internal\"\r\n - \"traefik.http.routers.api.tls=true\"\r\n - \"traefik.http.routers.api.tls.certresolver=letsencrypt\"\r\n command:\r\n - \"--api\"\r\n - \"--api.dashboard=true\"\r\n - \"--api.insecure=true\"\r\n - \"--providers.docker=true\"\r\n - \"--providers.docker.exposedByDefault=false\"\r\n - \"--entrypoints.http=true\"\r\n - \"--entrypoints.http.address=:80\"\r\n - \"--entrypoints.http.http.redirections.entrypoint.to=https\"\r\n - \"--entrypoints.http.http.redirections.entrypoint.scheme=https\"\r\n - \"--entrypoints.https=true\"\r\n - \"--entrypoints.https.address=:443\"\r\n - \"--certificatesResolvers.letsencrypt.acme.email=security@example.com\"\r\n - \"--certificatesResolvers.letsencrypt.acme.storage=acme.json\"\r\n - \"--certificatesResolvers.letsencrypt.acme.httpChallenge.entryPoint=http\"\r\n - \"--log=true\"\r\n - \"--log.level=INFO\"\r\n ports:\r\n - \"80:80\"\r\n - \"443:443\"\r\n - \"8080:8080\"\r\n networks:\r\n - internal_network\r\n - external_network\r\n volumes:\r\n - ./traefik/acme.json:/acme.json\r\n - /var/run/docker.sock:/var/run/docker.sock\r\n\r\n gitea:\r\n image: gitea/gitea:1.16\r\n container_name: gitea\r\n restart: unless-stopped\r\n depends_on:\r\n traefik:\r\n condition: service_started\r\n db:\r\n condition: service_started\r\n redis:\r\n condition: service_healthy\r\n environment:\r\n - APP_NAME=\"Gitea\"\r\n - RUN_MODE=prod\r\n - DOMAIN=code.example.com\r\n - SSH_DOMAIN=code.example.com\r\n - HTTP_PORT=3000\r\n - ROOT_URL=https://code.example.com\r\n - START_SSH_SERVER=true\r\n - SSH_PORT=222\r\n - SSH_LISTEN_PORT=22\r\n - DEFAULT_BRANCH=main\r\n - GITEA__database__DB_TYPE=postgres\r\n - GITEA__database__HOST=db:5432\r\n - GITEA__database__NAME=gitea\r\n - GITEA__database__USER=postgres\r\n - GITEA__database__PASSWD=\u003Cpg-password>\r\n - GITEA__cache__ENABLED=true\r\n - GITEA__cache__ADAPTER=redis\r\n - GITEA__cache__HOST=redis://redis:6379/0?pool_size=100&idle_timeout=180s\r\n - GITEA__cache__ITEM_TTL=24h\r\n - GITEA__webhook__ALLOWED_HOST_LIST=*\r\n labels:\r\n - \"traefik.enable=true\"\r\n - \"traefik.http.routers.gitea.rule=Host(`code.example.com`)\"\r\n - \"traefik.http.routers.gitea.entrypoints=https\"\r\n - \"traefik.http.routers.gitea.tls.certresolver=letsencrypt\"\r\n - \"traefik.http.routers.gitea.service=gitea-service\"\r\n - \"traefik.http.services.gitea-service.loadbalancer.server.port=3000\"\r\n ports:\r\n - \"222:22\"\r\n networks:\r\n - internal_network\r\n volumes:\r\n - gitea-data:/data\r\n - /etc/timezone:/etc/timezone:ro\r\n - /etc/localtime:/etc/localtime:ro\r\n\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:latest\r\n container_name: woodpecker-server\r\n restart: unless-stopped\r\n depends_on:\r\n gitea:\r\n condition: service_started\r\n environment:\r\n - WOODPECKER_OPEN=true\r\n - WOODPECKER_ORGS=code\r\n - WOODPECKER_ADMIN=jane,alice\r\n - WOODPECKER_REPO_OWNERS=my-org\r\n - WOODPECKER_HOST=https://ci.example.com\r\n - WOODPECKER_GITEA=true\r\n - WOODPECKER_GITEA_URL=https://code.example.com\r\n - WOODPECKER_GITEA_CLIENT=\u003Cgitea-oauth2-client-id>\r\n - WOODPECKER_GITEA_SECRET=\u003Cgitea-oauth2-secret>\r\n - WOODPECKER_AGENT_SECRET=\u003Cwoodpecker-agent-secret>\r\n labels:\r\n - \"traefik.enable=true\"\r\n - \"traefik.http.routers.woodpecker.rule=Host(`ci.example.com`)\"\r\n - \"traefik.http.routers.woodpecker.entrypoints=https\"\r\n - \"traefik.http.routers.woodpecker.tls.certresolver=letsencrypt\"\r\n - \"traefik.http.routers.woodpecker.service=woodpecker-service\"\r\n - \"traefik.http.services.woodpecker-service.loadbalancer.server.port=8000\"\r\n networks:\r\n - internal_network\r\n volumes:\r\n - woodpecker-server-data:/var/lib/woodpecker/\r\n\r\n woodpecker-agent:\r\n image: woodpeckerci/woodpecker-agent:latest\r\n command: agent\r\n container_name: woodpecker-agent\r\n restart: unless-stopped\r\n depends_on:\r\n woodpecker-server:\r\n condition: service_started\r\n environment:\r\n - WOODPECKER_SERVER=woodpecker-server:9000\r\n - WOODPECKER_AGENT_SECRET=\u003Cwoodpecker-agent-secret>\r\n networks:\r\n - internal_network\r\n volumes:\r\n - /var/run/docker.sock:/var/run/docker.sock\r\n\r\n db:\r\n […]\r\n\r\n redis:\r\n […]\r\n\r\nvolumes:\r\n db:\r\n gitea-data:\r\n woodpecker-server-data:\r\n\r\nnetworks:\r\n external_network:\r\n internal_network:\r\n internal: true\r\n```\r\n\r\n\u003C/details>\r\n\r\n\r\n### Additional context\r\n\r\n```shell\r\nThe Docker Compose logs show the attempted connection to Gitea and its resulting error output:\r\n\r\n\r\nwoodpecker-server | {\"level\":\"error\",\"message\":\"cannot authenticate user. Post \\\"https://code.example.com/login/oauth/access_token\\\": dial tcp XXX.XXX.XXX.XXX:443: i/o timeout\"}\r\n```\r\n```\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).",[3237],{"name":3238,"color":3239},"documentation","7D625D",856,"traefik: Woodpecker login via Gitea & OAuth2 times out","2023-11-04T14:56:50Z","https://github.com/woodpecker-ci/woodpecker/issues/856",0.7192338,{"description":3246,"labels":3247,"number":3251,"owner":3158,"repository":3159,"state":3184,"title":3252,"updated_at":3253,"url":3254,"score":3255},"### Component\n\nweb-ui\n\n### Describe the bug\n\ni can't change any settings in my repositories\r\neven though i'm set as an admin\r\n\r\nhttps://user-images.githubusercontent.com/35614734/143661066-9392eb98-0548-4029-b157-272d812f15a6.mp4\r\n\r\n \n\n### System Info\n\n```shell\nversion: '3.3'\r\nservices:\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:latest\r\n ports:\r\n - 127.0.0.1:9002:8000\r\n volumes:\r\n - ./woodpecker:/var/lib/woodpecker/\r\n environment:\r\n - 'WOODPECKER_ADMIN=FarisZR'\r\n - 'WOODPECKER_HOST=https://cd.site.test'\r\n - 'WOODPECKER_GITEA=true'\r\n - 'WOODPECKER_GITEA_URL=https://codeberg.org'\r\n - 'WOODPECKER_GITEA_CLIENT=xxxxx'\r\n - 'WOODPECKER_GITEA_SECRET=xxxxxx'\r\n - 'WOODPECKER_AGENT_SECRET=xxxxxxx'\r\n\r\n\r\n woodpecker-agent:\r\n image: woodpeckerci/woodpecker-agent:latest\r\n command: agent\r\n restart: always\r\n depends_on:\r\n - woodpecker-server\r\n volumes:\r\n - /var/run/docker.sock:/var/run/docker.sock\r\n environment:\r\n - WOODPECKER_SERVER=woodpecker-server:9000 \r\n - 'WOODPECKER_AGENT_SECRET=xxxxxxx'\r\n - WOODPECKER_BACKEND=docker\n```\n\n\n### Additional context\n\n```shell\nerrors in logs:\r\n\r\n\r\nwoodpecker-server_1 | {\"level\":\"warn\",\"error\":\"sql: no rows in result set\",\"time\":\"2021-11-26T22:56:52Z\"}\r\n\r\nwoodpecker-agent_1 | {\"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\":\"2021-11-26T23:06:24Z\",\"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\\\"\"}\n```\n\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).",[3248],{"name":3249,"color":3250},"duplicate","9D1C99",547,"insufficient privileges when changing any settings","2021-11-27T00:55:04Z","https://github.com/woodpecker-ci/woodpecker/issues/547",0.7204877,["Reactive",3257],{},["Set"],["ShallowReactive",3260],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJAg25izS1k3kdUSC7-PjmR6BenmJYBPnTIEPmKhuVFY":-1},"/woodpecker-ci/woodpecker/5339"]