\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]",[3072],{"name":3039,"color":3040},5321,"plugin-docker-buildx insecure with PLUGIN_BUILDKIT_DRIVEROPT image not work after version 6","2025-07-14T03:09:06Z","https://github.com/woodpecker-ci/woodpecker/issues/5321",0.77242523,{"description":3079,"labels":3080,"number":3086,"owner":3028,"repository":3029,"state":3087,"title":3088,"updated_at":3089,"url":3090,"score":3091},"to make sure on agent restart to also have the newest default images, we should pull them.\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/master/shared/constant/constant.go",[3081,3082,3083],{"name":3062,"color":3063},{"name":3050,"color":3051},{"name":3084,"color":3085},"good first issue","76ea72",947,"closed","Pull default images on agent start","2022-08-14T19:22:36Z","https://github.com/woodpecker-ci/woodpecker/issues/947",0.60498303,{"description":3093,"labels":3094,"number":3098,"owner":3028,"repository":3029,"state":3087,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Clear and concise description of the problem\r\n\r\nWhen I set up pipeline like\r\n```\r\npipeline:\r\n test:\r\n image: alpine\r\n commands:\r\n - echo Hello\r\n```\r\nor like\r\n```\r\npipeline:\r\n test:\r\n image: alpine:latest\r\n commands:\r\n - echo Hello\r\n```\r\nI'm expecting [behavior](https://kubernetes.io/docs/concepts/containers/images/#imagepullpolicy-defaulting):\r\n> if you omit the imagePullPolicy field, and the tag for the container image is :latest, imagePullPolicy is automatically set to Always;\r\n> if you omit the imagePullPolicy field, and you don't specify the tag for the container image, imagePullPolicy is automatically set to Always;\r\n\r\nIn other words I'm expecting [checking for a new image always](https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy), not sticking with current cached image.\r\n\r\nI know that there is the [statement in docs](https://woodpecker-ci.org/docs/next/usage/pipeline-syntax#image)\r\n> Woodpecker does not automatically upgrade container images. Use `pull: true`.\r\n\r\nand `ImagePullPolicy` [is always set](https://github.com/woodpecker-ci/woodpecker/blob/3d435a9cb73cd8f49f030d58568cae7890f2c5d2/pipeline/backend/kubernetes/pod.go#L46)... So, technically all works as intendent... But I didn't set image pull policy explicitly and expected default Kubernetes behavior.\r\n\r\nIs it good idea to align with Kubernetes [Default image pull policy](https://kubernetes.io/docs/concepts/containers/images/#imagepullpolicy-defaulting)? At least it shouldn't be so difficult to implement. What do you think?\r\n\r\n### Suggested solution\r\n\r\nIf step's `pull: false` or is not set, then do not fill `v1.Container.ImagePullPolicy` field.\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\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 request the same feature to avoid creating a duplicate.",[3095],{"name":3096,"color":3097},"feature","180DBE",1912,"Respecting Kubernetes Default image pull policy","2023-07-07T20:38:22Z","https://github.com/woodpecker-ci/woodpecker/issues/1912",0.74357176,{"description":3104,"labels":3105,"number":3110,"owner":3028,"repository":3029,"state":3087,"title":3111,"updated_at":3112,"url":3113,"score":3114},"### Clear and concise description of the problem\r\n\r\nAs we can read in the documentation the next version will drop Gogs support. The truth is that it would be very interesting to reconsider this, let me explain.\r\n\r\nIt is true that nowadays Gogs is widely surpassed by Forgejo, but it is also true that if what you need is a simple web interface without too many frills, it is preferable to use Gogs rather than Forgejo. Gogs is much simpler and for those of us who have a local instance and don't need more than a few repositories, Gogs is the best choice. In such cases, using Forgejo would be \"shooting flies with cannons\".\r\n\r\n### Suggested solution\r\n\r\nDon't drop Gogs support in next version.\r\n\r\n### Alternative\r\n\r\nThe truth is that there are not many other alternatives with the power of Gogs that are just as easy to use. It is true that there is cgit and gitolite, which together could be an alternative, but I think it is much easier to maintain an integration with Gogs (which in the end will be very similar to that of Forgejo) than one with gitolite.\r\n\r\n### Additional context\r\n\r\nThis is obviously a suggestion for consideration. I have created this issue because I have not found a similar one and because, if you do not see this need, it would be answered.\r\n\r\n### Validations\r\n\r\n- [X] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\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 request the same feature to avoid creating a duplicate.",[3106,3107],{"name":3096,"color":3097},{"name":3108,"color":3109},"blocked","AF9796",1894,"Reconsider Gogs support in next version","2023-08-08T08:10:55Z","https://github.com/woodpecker-ci/woodpecker/issues/1894",0.7569815,{"description":3116,"labels":3117,"number":3122,"owner":3028,"repository":3029,"state":3087,"title":3123,"updated_at":3124,"url":3125,"score":3126},"### Clear and concise description of the problem\n\nCurrently there is no way to limit where to limit agents where pipelines without any filter labels specified to run on.\n\n### Suggested solution\n\nAdd configuration option for woodpecker server to set default label filters that would be set for pipelines that has no filter set.\r\n\r\nThis could also be used as alternative to fix #2634\n\n### Alternative\n\nAs workaround this possible be also implemented in external configuration service but that seems not so straightforward and could be harder to implement\n\n### Additional context\n\nGitlab CI implements similar approach to allow for agents to set option that they are allowed to run \"untagged pipelines\"\n\n### Validations\n\n- [X] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\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 request the same feature to avoid creating a duplicate.",[3118,3121],{"name":3119,"color":3120},"server","5D7A92",{"name":3050,"color":3051},4324,"Allow configuration option to specify default filter labels","2024-11-14T21:23:44Z","https://github.com/woodpecker-ci/woodpecker/issues/4324",0.76087946,{"description":3128,"labels":3129,"number":3130,"owner":3028,"repository":3029,"state":3087,"title":3131,"updated_at":3132,"url":3133,"score":3134},"### 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.7620097,["Reactive",3136],{},["Set"],["ShallowReactive",3139],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f24Rm2wgtZMThU2Xd4pTsEBbZgyWoOZ0GCFABAgGLSwY":-1},"/woodpecker-ci/woodpecker/1508"]