\r\n\n\n### Steps to reproduce\n\n.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n\"next-d126cf9e35\"\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]",[2904,2907],{"name":2905,"color":2906},"bug","d73a4a",{"name":2908,"color":2909},"ui","46DEA2",4677,"woodpecker-ci","woodpecker","open","`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.71590424,{"description":2919,"labels":2920,"number":2927,"owner":2911,"repository":2912,"state":2913,"title":2928,"updated_at":2929,"url":2930,"score":2931},"https://github.com/woodpecker-ci/woodpecker/blob/4456da99c56437ef49c799a047ad3518023e6ce3/pipeline/rpc/peer.go#L54",[2921,2924],{"name":2922,"color":2923},"documentation","7D625D",{"name":2925,"color":2926},"refactor","4f8cc9",3322,"Rename Interface to actully reflect what it is used for","2024-02-07T00:03:34Z","https://github.com/woodpecker-ci/woodpecker/issues/3322",0.7276368,{"description":2933,"labels":2934,"number":2941,"owner":2911,"repository":2912,"state":2913,"title":2942,"updated_at":2943,"url":2944,"score":2945},"e.g. like https://github.com/woodpecker-ci/woodpecker/pull/3086 create pull tags.\r\n\r\njust clean them up if the pull gets closed",[2935,2938],{"name":2936,"color":2937},"enhancement","7E1FE4",{"name":2939,"color":2940},"build","6AB8BA",3087,"build: delete pr images on pull close","2023-12-31T07:28:26Z","https://github.com/woodpecker-ci/woodpecker/issues/3087",0.73790693,{"description":2947,"labels":2948,"number":2953,"owner":2911,"repository":2912,"state":2913,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Component\r\n\r\nserver, agent\r\n\r\n### Describe the bug\r\n\r\nThis is mainly a summary issue of https://github.com/woodpecker-ci/woodpecker/issues/833, https://github.com/woodpecker-ci/woodpecker/issues/2062, https://github.com/woodpecker-ci/woodpecker/issues/2911\rand #4349\n\r\nI've been trying to debug this without real success.\r\n\r\nI've been using the local backend, and can do the following observations:\r\n- cancel pipeline while running: completely broken. The commands are finished, the step is marked as success, the pipeline too (https://github.com/woodpecker-ci/woodpecker/issues/2911)\r\n- cancelling a pending pipeline seems to work for me\r\n\r\nOn ci.woodpecker-ci.org, I can see (uses docker backend):\r\n- cancel pending pipeline, agent is available: the pipeline starts anyways (this probably is #2062)\r\n- cancel running pipeline: works in general, but new status is failing but should be killed\r\n\r\n### System Info\r\n\r\n```shell\r\nnext\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/main/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).",[2949,2950],{"name":2905,"color":2906},{"name":2951,"color":2952},"summary","C3DC73",2875,"Fix pipeline cancelling","2024-12-08T12:10:57Z","https://github.com/woodpecker-ci/woodpecker/issues/2875",0.7384965,{"description":2959,"labels":2960,"number":2965,"owner":2911,"repository":2912,"state":2966,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Clear and concise description of the problem\r\n\r\nI'm trying to run a container image build step in my pipeline that uses [buildah](https://quay.io/repository/buildah/stable?tab=info). I'm running into a lot of permission errors like this:\r\n\r\n```\r\ntime=\"2023-10-07T19:59:26Z\" level=error msg=\"writing \\\"0 0 4294967295\\\\n\\\" to /proc/17/uid_map: write /proc/17/uid_map: operation not permitted\"\r\ntime=\"2023-10-07T19:59:26Z\" level=error msg=\"(Unable to determine exit status)\"\r\n```\r\n\r\nAfter some experimentation with podman and buildah containers on my cluster, I have determined that I need to configure a few different settings at the Pod level for this to work:\r\n\r\n- `metadata.annotations`: I need to be able to set `container.apparmor.security.beta.kubernetes.io/\u003Ccontainer_name>` to use a custom apparmor profile for my buildah container. I would like to use the `WOODPECKER_BACKEND_K8S_POD_ANNOTATIONS` env variable, but since the container names are randomly generated I'm not sure how to make this work.\r\n- `spec.securityContext`: The only way I have found to make buildah work is to run it as non-root. This means that I need to set `runAsUser`, `runAsGroup`, and `fsGroup` on the Pod level `securityContext` (not the container level).\r\n\r\n### Suggested solution\r\n\r\nAdding support for `securityContext` seems like it should be fairly straightforward. We could just follow that same approach that is currently used for `resources`, `nodeSelector`, etc. [documented here](https://woodpecker-ci.org/docs/next/administration/backends/kubernetes#resources).\r\n\r\nThe AppArmor profile is trickier since the container name needs to be included in the annotation key. I'm imagining a configuration like `backend_options.kubernetes.appArmorProfile` that could take all of the possible values for the annotation [documented here](https://kubernetes.io/docs/tutorials/security/apparmor/). Then, the pod generation logic would just look for this configuration and add the appropriate annotation if it's found.\r\n\r\n### Alternative\r\n\r\nI could disable AppArmor entirely, but that's not really advisable for a production environment. I could also try to find a way to get the buildah container running as root (it should be possible), but again, that's not ideal from a security perspective.\r\n\r\n### Additional context\r\n\r\nThis is somewhat of a follow up from #2510. I'm trying to get Woodpecker to run on my kubeadm/CRI-O based cluster running on Debian which I believe makes me some kind of leprechaun/unicorn/lochness monster. There definitely aren't many of us out there.\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/main/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.",[2961,2962],{"name":2936,"color":2937},{"name":2963,"color":2964},"backend/kubernetes","bfdadc",2545,"closed","Support AppArmor annotations and securityContext in kubernetes backend","2024-01-12T22:32:26Z","https://github.com/woodpecker-ci/woodpecker/issues/2545",0.67677677,{"description":2972,"labels":2973,"number":2975,"owner":2911,"repository":2912,"state":2966,"title":2976,"updated_at":2977,"url":2978,"score":2979},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nWhen having a backend error in the config, i.e. a malformed env var, the step and build are marked as successful even though they should be marked as \"failed\". \r\n\r\n\r\n\r\n\r\nk8s backend\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-6ab9f802\"}\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).",[2974],{"name":2905,"color":2906},1871,"Build is marked as \"successful\" although a backend error occurred","2025-01-10T21:25:48Z","https://github.com/woodpecker-ci/woodpecker/issues/1871",0.68623674,{"description":2981,"labels":2982,"number":2989,"owner":2911,"repository":2912,"state":2966,"title":2990,"updated_at":2991,"url":2992,"score":2993},"~~add sub-command to server to migrate databases.~~ add env-far/flag to import from old db; a dedicated subcomand could be optionaly added, let's see\r\n\r\nmake it possible to migrate a sqlite3 instance into a ... MySQL and so on.\r\n\r\nIt is could happen that you at some point decide you like to scale ...",[2983,2986],{"name":2984,"color":2985},"server","5D7A92",{"name":2987,"color":2988},"feature","180DBE",924,"Add option to migrate database","2025-01-13T14:27:29Z","https://github.com/woodpecker-ci/woodpecker/issues/924",0.6997058,{"description":2995,"labels":2996,"number":2998,"owner":2911,"repository":2912,"state":2966,"title":2999,"updated_at":3000,"url":3001,"score":3002},"### Component\r\n\r\nserver, web-ui\r\n\r\n### Describe the bug\r\n\r\nHi, I have problem with my woodpecker instance. I'm using Github to provide OAuth2 Authorization. But the problem I cannot log in to the app. When I clicking \"Log in\" button, it returns to the same screen. Sometimes when I do many clicks in small amount time I need reatuhorize it in Github.\r\n\r\nInstance is hidden with ngnix proxy manager. \r\n\r\nMy docker compose looks like this:\r\n```\r\nservices:\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:latest\r\n expose:\r\n - 8000\r\n - 9000\r\n volumes:\r\n - ./woodpecker-server-data:/var/lib/woodpecker/\r\n environment:\r\n - WOODPECKER_OPEN=false\r\n - WOODPECKER_HOST=${WOODPECKER_HOST}\r\n - WOODPECKER_GITHUB=true\r\n - WOODPECKER_GITHUB_CLIENT=${WOODPECKER_GITHUB_CLIENT}\r\n - WOODPECKER_GITHUB_SECRET=${WOODPECKER_GITHUB_SECRET}\r\n - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}\r\n - WOODPECKER_ADMIN=${WOODPECKER_ADMIN}\r\n - WOODPECKER_REPO_OWNERS=${WOODPECKER_REPO_OWNERS}\r\n networks:\r\n - ngnix-internal\r\n - composehook-internal\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 - ./woodpecker-agent-config:/etc/woodpecker\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=${WOODPECKER_AGENT_SECRET}\r\n - WOODPECKER_BACKEND_DOCKER_NETWORK=composehook-internal\r\n networks:\r\n - ngnix-internal\r\n - composehook-internal\r\nnetworks:\r\n ngnix-internal:\r\n external: true\r\n name: ngnix-internal\r\n composehook-internal:\r\n external: true\r\n name: composehook-internal\r\n```\r\n\r\nIn logs I haven't see something weird or wrong.\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\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 [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]",[2997],{"name":2905,"color":2906},3689,"Stuck on login screen. ","2024-06-21T08:20:32Z","https://github.com/woodpecker-ci/woodpecker/issues/3689",0.70987,{"description":3004,"labels":3005,"number":3007,"owner":2911,"repository":2912,"state":2966,"title":3008,"updated_at":3009,"url":3010,"score":3011},"### Component\r\n\r\nother\r\n\r\n### Describe the bug\r\n\r\nEnhance pipeline list https://github.com/woodpecker-ci/woodpecker/pull/3898 was reverted before release.\r\n\r\n### Steps to reproduce\r\n\r\n1. Go to [Releases](https://github.com/woodpecker-ci/woodpecker/releases) page\r\n2. and see #3898 is mentioned as enhancement, there is no #3926\r\n\r\n### Expected behavior\r\n\r\nThere should not be #3898 in release notes.\r\n\r\n### System Info\r\n\r\nRelated to 2.7.0\r\n\r\n\r\n### Additional context\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/pull/3926\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]",[3006],{"name":2905,"color":2906},3998,"Remove 3898 from release notes","2024-08-04T23:34:14Z","https://github.com/woodpecker-ci/woodpecker/issues/3998",0.720479,{"description":3013,"labels":3014,"number":3022,"owner":2911,"repository":2912,"state":2966,"title":3023,"updated_at":3024,"url":3025,"score":3026},"- mention how settings are de-serialized\r\n- mention build-in-env-vars\r\n- mention best practics\r\n- mention multiarch build, as official immages try to always have linux/amd64 & linux/arm64 images, and so other plugins should try to do so to",[3015,3018,3019],{"name":3016,"color":3017},"plugin","887B27",{"name":2922,"color":2923},{"name":3020,"color":3021},"good first issue","76ea72",1389,"Document how to create an own plugin","2023-12-30T20:24:09Z","https://github.com/woodpecker-ci/woodpecker/issues/1389",0.7289998,["Reactive",3028],{},["Set"],["ShallowReactive",3031],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMY7bIu1fe-WB74LD6om1ZG5xbPnA1LpfTo91Qk0XpzQ":-1},"/woodpecker-ci/woodpecker/2236"]