\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]",[2865,2868],{"name":2866,"color":2867},"bug","d73a4a",{"name":2869,"color":2870},"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.7308698,{"description":2880,"labels":2881,"number":2886,"owner":2872,"repository":2873,"state":2874,"title":2887,"updated_at":2888,"url":2889,"score":2890},"### Component\n\nserver\n\n### Describe the bug\n\nError when enabling Gitea repository in Woodpecker CI:\n\n`could not create/update repo in store. error=\"pq: duplicate key value violates unique constraint \\\"UQE_repos_name\\\"\"`\n\nThere are no records with forge_id 0 in orgs table where we had similar problems\n\n### Steps to reproduce\n\n1. Press \"Enable\" in repository list\n2. Webhook is created\n3. Record in database can not be updated (possible tries to insert new one instead of updating?)\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"3.3.0\"}\n```\n\n### Additional context\n\nPostgreSQL database, Gitea forge integration\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]",[2882,2883],{"name":2866,"color":2867},{"name":2884,"color":2885},"server","5D7A92",4935,"Activating repository error that failed to activate becauce of UQE_repos_name constraint","2025-03-11T14:11:01Z","https://github.com/woodpecker-ci/woodpecker/issues/4935",0.7453539,{"description":2892,"labels":2893,"number":2900,"owner":2872,"repository":2873,"state":2874,"title":2901,"updated_at":2902,"url":2903,"score":2904},"I think we should have a look at https://nextcloud.com/contribute/ and chery-pick some ideas from that",[2894,2897],{"name":2895,"color":2896},"documentation","7D625D",{"name":2898,"color":2899},"enhancement","7E1FE4",4113,"Improve docs about starting to contribute","2024-09-15T09:47:05Z","https://github.com/woodpecker-ci/woodpecker/issues/4113",0.74611235,{"description":2906,"labels":2907,"number":2911,"owner":2872,"repository":2873,"state":2874,"title":2912,"updated_at":2913,"url":2914,"score":2915},"we should create a dedicated module who handle the shutdown context logic ...\r\n\r\nand make it so we dont have to switch out an global context but rather influence it ...\r\n\r\nbased on #3895 and #3896 pre-work",[2908],{"name":2909,"color":2910},"refactor","4f8cc9",3907,"Refactor note: move shutdown context creation into own module","2024-07-14T00:27:20Z","https://github.com/woodpecker-ci/woodpecker/issues/3907",0.7492927,{"description":2917,"labels":2918,"number":2923,"owner":2872,"repository":2873,"state":2874,"title":2924,"updated_at":2925,"url":2926,"score":2927},"we currently don't have a concept how to translate/interpreter the services into \"local backend\" and just ignore them.\r\n\r\nwe should have it that way so it works very similar to what the user know with docker or kube backend.",[2919,2920],{"name":2898,"color":2899},{"name":2921,"color":2922},"backend/local","bfdadc",3095,"Implement services for local backend","2025-02-10T13:40:24Z","https://github.com/woodpecker-ci/woodpecker/issues/3095",0.757306,{"description":2929,"labels":2930,"number":2932,"owner":2872,"repository":2873,"state":2874,"title":2933,"updated_at":2934,"url":2935,"score":2936},"https://github.com/rs/zerolog#contextcontext-integration\r\n\r\nthis allow us to have \"stacktrace\" like logs where we can append log prefixes and pass down",[2931],{"name":2909,"color":2910},2116,"Refactor: use zerolog with context if posible ","2024-06-23T05:42:09Z","https://github.com/woodpecker-ci/woodpecker/issues/2116",0.77044517,{"description":2938,"labels":2939,"number":2941,"owner":2872,"repository":2873,"state":2942,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### 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]",[2940],{"name":2866,"color":2867},3689,"closed","Stuck on login screen. ","2024-06-21T08:20:32Z","https://github.com/woodpecker-ci/woodpecker/issues/3689",0.69989765,{"description":2948,"labels":2949,"number":2951,"owner":2872,"repository":2873,"state":2942,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### 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).",[2950],{"name":2866,"color":2867},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.72631866,{"description":2957,"labels":2958,"number":2962,"owner":2872,"repository":2873,"state":2942,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### 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.",[2959,2960],{"name":2898,"color":2899},{"name":2961,"color":2922},"backend/kubernetes",2545,"Support AppArmor annotations and securityContext in kubernetes backend","2024-01-12T22:32:26Z","https://github.com/woodpecker-ci/woodpecker/issues/2545",0.737402,{"description":2968,"labels":2969,"number":2971,"owner":2872,"repository":2873,"state":2942,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Component\n\nserver\n\n### Describe the bug\n\nI have various repo's with cron jobs set.\nThese cron jobs now fail to start but running the pipelines manually works.\n\nLast working version is `next-8e99551d18`.\n\n\n### Steps to reproduce\n\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nVersion: next-00aa968afa\n```\n\n### Additional context\n\n```\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:336\",\"message\":\"queue: trying to assign task: 3334 with deps []\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:369\",\"message\":\"queue: pending right now: 3334\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:336\",\"message\":\"queue: trying to assign task: 3334 with deps []\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:369\",\"message\":\"queue: pending right now: 3334\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:336\",\"message\":\"queue: trying to assign task: 3334 with deps []\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:369\",\"message\":\"queue: pending right now: 3334\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:336\",\"message\":\"queue: trying to assign task: 3334 with deps []\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:369\",\"message\":\"queue: pending right now: 3334\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:336\",\"message\":\"queue: trying to assign task: 3334 with deps []\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:369\",\"message\":\"queue: pending right now: 3334\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:336\",\"message\":\"queue: trying to assign task: 3334 with deps []\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:369\",\"message\":\"queue: pending right now: 3334\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:336\",\"message\":\"queue: trying to assign task: 3334 with deps []\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:369\",\"message\":\"queue: pending right now: 3334\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:336\",\"message\":\"queue: trying to assign task: 3334 with deps []\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:369\",\"message\":\"queue: pending right now: 3334\"}\n{\"level\":\"debug\",\"time\":\"2025-01-31T14:17:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/queue/fifo.go:336\",\"message\":\"queue: trying to assign task: 3334 with deps []\"}\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/faq#which-version-of-woodpecker-should-i-use]",[2970],{"name":2866,"color":2867},4797,"Cron fail to start but manual run works in latest version.","2025-01-31T14:47:29Z","https://github.com/woodpecker-ci/woodpecker/issues/4797",0.753323,["Reactive",2977],{},["Set"],["ShallowReactive",2980],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fwjylwlIH11O0nFT0zKHqodoeGGhY_it1a4_THWTNhaU":-1},"/woodpecker-ci/woodpecker/4939"]