\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]",[3055],{"name":3019,"color":3020},5321,"closed","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.6675884,{"description":3063,"labels":3064,"number":3066,"owner":3022,"repository":3023,"state":3057,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### 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).",[3065],{"name":3019,"color":3020},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.68615186,{"description":3072,"labels":3073,"number":3078,"owner":3022,"repository":3023,"state":3057,"title":3079,"updated_at":3080,"url":3081,"score":3082},"### 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]",[3074,3075],{"name":3019,"color":3020},{"name":3076,"color":3077},"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.6930284,{"description":3084,"labels":3085,"number":3087,"owner":3022,"repository":3023,"state":3057,"title":3088,"updated_at":3089,"url":3090,"score":3091},"### 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]",[3086],{"name":3019,"color":3020},4934,"Runtime SIGSEGV error in agent","2025-03-14T13:04:55Z","https://github.com/woodpecker-ci/woodpecker/issues/4934",0.70398366,{"description":3093,"labels":3094,"number":3099,"owner":3022,"repository":3023,"state":3057,"title":3100,"updated_at":3101,"url":3102,"score":3103},"This worked with WP 2.3 and Kubernetes backend:\r\n\r\n```\r\n publish:\r\n image: woodpeckerci/plugin-docker-buildx\r\n settings:\r\n repo: *repo\r\n tags: 8h\r\n```\r\n\r\nUsing WP 2.4 the docker daemon does not start.\r\n\r\nDebugging the Pod manifest I see an empty security context and the docker daemon does not start.\r\n\r\nThis works with WP 2.4.1 but is not so user friendly:\r\n\r\n```\r\n publish:\r\n image: woodpeckerci/plugin-docker-buildx\r\n privileged: true\r\n backend_options:\r\n kubernetes:\r\n securityContext:\r\n privileged: true\r\n settings:\r\n repo: *repo\r\n tags: 8h\r\n daemon.debug: \"true\"\r\n```\r\n\r\n\r\nSee also: https://github.com/woodpecker-ci/woodpecker/issues/3482#issuecomment-2015672185_\r\n ",[3095,3096],{"name":3019,"color":3020},{"name":3097,"color":3098},"backend/kubernetes","bfdadc",3537,"Woodpecker 2.4 breaks privileged steps/plugins with Kubernetes backend","2024-05-30T16:53:05Z","https://github.com/woodpecker-ci/woodpecker/issues/3537",0.70824975,{"description":3105,"labels":3106,"number":3110,"owner":3022,"repository":3023,"state":3057,"title":3111,"updated_at":3112,"url":3113,"score":3114},"# Required open issues / PRs\r\n- [x] #4314 fixed\r\n- [x] v2.8.0 with https://github.com/woodpecker-ci/woodpecker/issues/4306 released\r\n- [x] service settings (https://github.com/woodpecker-ci/woodpecker/pull/4336)\r\n- [ ] ...\r\n\r\n# Breaking changes (sorted by impact for users)\r\n\r\n- change of webhook => requires repair all #4013 \r\n- removed deprecated keywords: \r\n - `pipeline`, `platform`, `branches`, `steps.[name].secrets` #4363 #3916 \r\n - `steps.[name].group`, removed `include` / `exclude` from when filter #4016\r\n- removed privileged plugins: `plugins/docker`, `plugins/gcr`, `plugins/ecr`, `woodpeckerci/plugin-docker-buildx` #3846\r\n- removed alternative names for secrets, use `environment` with `from_secret` #4016\r\n- removed `environment` for `when.evaluate` #4016\r\n- removed slice definition for env vars #4016\r\n- #4005\r\n- #3785\r\n- stopped secrets from being uppercased #4053\r\n- replaced cli `registry` command with `repo registry` #4017\r\n- some changes / removals of api routes / json properties #3968\r\n- cron not using seconds anymore #3785\r\n- (Left out less relevant changes, Please add other impact-full changes)\r\n\r\n# Tasks before releasing\r\n- Update go imports to `\"go.woodpecker-ci.org/woodpecker/v3/...\"`\r\n- Check and adjust migration docs, so users can simply follow and get to the new version. testing\r\n- Create new docs version 3.0\r\n- Create blog post\r\n- Test version \r\n- Post on social media",[3107],{"name":3108,"color":3109},"governance","A46EFE",4320,"Release plan for v3.0.0","2025-01-18T23:31:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4320",0.7103561,{"description":3116,"labels":3117,"number":3119,"owner":3022,"repository":3023,"state":3057,"title":3120,"updated_at":3121,"url":3122,"score":3123},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nWoodpecker failed to set Kubernetes resources requests and limits if it's specified with a number instead of string.\r\n\r\n```yaml\r\n backend_options:\r\n kubernetes:\r\n resources:\r\n requests:\r\n cpu: 2000m\r\n memory: 6Gi\r\n nvidia.com/gpu: 1\r\n nvidia.com/gpumem: 2000\r\n limits:\r\n cpu: 2000m\r\n memory: 6Gi\r\n nvidia.com/gpu: 1\r\n nvidia.com/gpumem: 2000\r\n```\r\n\r\nresults in\r\n\r\n```yaml\r\n Limits:\r\n cpu: 2\r\n memory: 6Gi\r\n Requests:\r\n cpu: 2\r\n memory: 6Gi\r\n```\r\n\r\nwhile \r\n\r\n```yaml\r\n backend_options:\r\n kubernetes:\r\n resources:\r\n requests:\r\n cpu: 2000m\r\n memory: 6Gi\r\n nvidia.com/gpu: '1'\r\n nvidia.com/gpumem: '2000'\r\n limits:\r\n cpu: 2000m\r\n memory: 6Gi\r\n nvidia.com/gpu: '1'\r\n nvidia.com/gpumem: '2000'\r\n```\r\n\r\nresults in\r\n\r\n```yaml\r\n Limits:\r\n cpu: 2\r\n memory: 6Gi\r\n nvidia.com/gpu: 1\r\n nvidia.com/gpumem: 2k\r\n Requests:\r\n cpu: 2\r\n memory: 6Gi\r\n nvidia.com/gpu: 1\r\n nvidia.com/gpumem: 2k\r\n```\r\n\r\n\r\n### Steps to reproduce\r\n\r\n1. Install Woodpecker Agent on a Kubernetes with NVIDIA GPU;\r\n2. Run the workflow.\r\n\r\n### Expected behavior\r\n\r\nAll values valid for Kubernetes YAML should be accepted, including numbers for this scenario.\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.8.0\"}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nLog\r\n\r\n```json\r\n{\"level\":\"error\",\"error\":\"4 error(s) decoding:\\n\\n* 'resources.limits[nvidia.com/gpu]' expected type 'string', got unconvertible type 'float64', value: '1'\\n* 'resources.limits[nvidia.com/gpumem]' expected type 'string', got unconvertible type 'float64', value: '2000'\\n* 'resources.requests[nvidia.com/gpu]' expected type 'string', got unconvertible type 'float64', value: '1'\\n* 'resources.requests[nvidia.com/gpumem]' expected type 'string', got unconvertible type 'float64', value: '2000'\",\"time\":\"2024-12-02T20:00:16Z\",\"message\":\"could not parse backend options\"}\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]",[3118],{"name":3019,"color":3020},4504,"Kubernetes resources requests are ignored if numbers are used","2024-12-16T17:37:40Z","https://github.com/woodpecker-ci/woodpecker/issues/4504",0.7103746,["Reactive",3125],{},["Set"],["ShallowReactive",3128],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fn3mXJ8ACW0OIoQ4Uk26CuoaZNowXQFrJFg8dWOsGB-Y":-1},"/woodpecker-ci/woodpecker/5145"]