\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]",[3076],{"name":3019,"color":3020},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.69996583,{"description":3083,"labels":3084,"number":3089,"owner":3022,"repository":3023,"state":3033,"title":3090,"updated_at":3091,"url":3092,"score":3093},"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 ",[3085,3086],{"name":3019,"color":3020},{"name":3087,"color":3088},"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.7001864,{"description":3095,"labels":3096,"number":3097,"owner":3022,"repository":3023,"state":3033,"title":3098,"updated_at":3099,"url":3100,"score":3101},"### 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.7038802,{"description":3103,"labels":3104,"number":3109,"owner":3022,"repository":3023,"state":3033,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### Component\n\nother\n\n### Describe the bug\n\n```yaml\nsteps:\n - name: push to ecr dev\n image: woodpeckerci/plugin-docker-buildx:6.0.0\n settings:\n mtu: 1500\n registry: \u003Cregistry>\n dockerfile: ./Dockerfile\n build_args:\n WWWGROUP: \"1000\"\n SUPERVISORD_GO_OS: Linux_ARM64\n repo: \u003Crepo>\n aws_region: \u003Cregion>\n tags:\n - dev\n aws_access_key_id: \u003Ckey>\n aws_secret_access_key: \u003Csecret>\n backend_options:\n kubernetes:\n resources:\n requests:\n memory: 1200Mi\n cpu: 1200m\n limits:\n memory: 1500Mi\n cpu: 1600m\n when:\n branch:\n - develop\n event:\n - push\n```\n\n\n### Steps to reproduce\n\nThis yaml produces docker args `--build-arg 1000 --build-arg Linux_ARM64`.\n\n### Expected behavior\n\nIt should produce docker args `--build-arg WWWGROUP=1000 --build-arg SUPERVISORD_GO_OS=Linux_ARM64`.\n\n### System Info\n\n```shell\nWoodpecker helm chart 3.1.0\n\nwoodpeckerci/plugin-docker-buildx v6.0.0\n```\n\n### Additional context\n\nWorkaround:\n\n```yaml\nsteps:\n - name: push to ecr dev\n image: woodpeckerci/plugin-docker-buildx:6.0.0\n settings:\n mtu: 1500\n registry: \u003Cregistry>\n dockerfile: ./Dockerfile\n build_args:\n WWWGROUP: WWWGROUP=1000\n SUPERVISORD_GO_OS: SUPERVISORD_GO_OS=Linux_ARM64\n repo: \u003Crepo>\n aws_region: \u003Cregion>\n tags:\n - dev\n aws_access_key_id: \u003Ckey>\n aws_secret_access_key: \u003Csecret>\n backend_options:\n kubernetes:\n resources:\n requests:\n memory: 1200Mi\n cpu: 1200m\n limits:\n memory: 1500Mi\n cpu: 1600m\n when:\n branch:\n - develop\n event:\n - push\n```\n\nThis workaround produces `--build-arg WWWGROUP=1000 --build-arg SUPERVISORD_GO_OS=Linux_ARM64`, lol.\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]",[3105,3106],{"name":3019,"color":3020},{"name":3107,"color":3108},"plugin","887B27",5145,"Plugin plugin-docker-buildx v6 removes keys from build-arg","2025-05-04T10:42:17Z","https://github.com/woodpecker-ci/woodpecker/issues/5145",0.7039954,["Reactive",3115],{},["Set"],["ShallowReactive",3118],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fPjMBRp7_SpeFwj5rNUcp9W1TNXhwYjDZTvZL7mH0wkA":-1},"/woodpecker-ci/woodpecker/1918"]