\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]",[2919,2920],{"name":2868,"color":2869},{"name":2921,"color":2922},"ui","46DEA2",4677,"`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.7352408,{"description":2929,"labels":2930,"number":2938,"owner":2874,"repository":2875,"state":2876,"title":2939,"updated_at":2940,"url":2941,"score":2942},"The backend is currently executing based on stages consider using a dag instead.\r\n\r\nfollowup to https://github.com/woodpecker-ci/woodpecker/pull/2771",[2931,2932,2935],{"name":2909,"color":2910},{"name":2933,"color":2934},"enhancement","7E1FE4",{"name":2936,"color":2937},"engine","5319e7",3009,"Use DAG for steps in backend","2024-06-22T20:48:55Z","https://github.com/woodpecker-ci/woodpecker/issues/3009",0.7440898,{"description":2944,"labels":2945,"number":2950,"owner":2874,"repository":2875,"state":2876,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nI'm trying to get started with the Kubernetes backend (installed via the official helm chart). When I try to run a pipeline, the container gets stuck with CreateContainerError.\r\n\r\n```\r\nError: container create failed: chdir: No such file or directory\r\n```\r\n\r\nAfter some debugging, it seems like the issue is related to the `spec.workingDir` being set to a directory that doesn't exist at the time that the container is starting. I'm not exactly an expert here, but maybe we could leave the working dir unset and then change directories after the repo is cloned?\r\n\r\nI can provide more debugging information, if that would be help.\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-24204ecdeb\"}\r\n```\r\n\r\nThis is a vanilla Kubernetes 1.28.2 cluster installed via kubeadm. The nodes are Debian 12. The container runtime is CRI-O which was installed following the [install guide here](https://github.com/cri-o/cri-o/blob/v1.28.1/install.md#apt-based-operating-systems).\r\n\r\n\r\n### Additional context\r\n\r\nI'm running CRI-O (I'm not sure if that's relevant), and I discussed this issue a bit on the [CRI-O repo here](https://github.com/cri-o/cri-o/discussions/7338).\r\n\r\nI'm using Forgejo as my forge. If I comment out the `spec.workingDir` in the Pod yaml and attempt to run the Pod manually I get an error like:\r\n\r\n```\r\n+ git fetch --no-tags --depth=1 --filter=tree:0 origin +master:\r\nerror: RPC failed; HTTP 403 curl 22 The requested URL returned error: 403\r\nfatal: expected flush after ref listing\r\nexit status 128\r\n```\r\n\r\nI'm not sure if that's another issue or somehow related, but I thought it was worth mentioning.\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).",[2946,2947],{"name":2868,"color":2869},{"name":2948,"color":2949},"backend/kubernetes","bfdadc",2510,"Cannot run pipeline on Kubernetes: CreateContainerError","2025-04-02T06:36:59Z","https://github.com/woodpecker-ci/woodpecker/issues/2510",0.74677044,{"description":2956,"labels":2957,"number":2959,"owner":2874,"repository":2875,"state":2876,"title":2960,"updated_at":2961,"url":2962,"score":2963},"see https://github.com/woodpecker-ci/woodpecker/issues/558#issuecomment-987456959\r\n\r\nIt could happen that the original user who activated a repo reject there oauth2 access or left the project, dont have the rights anymore ...\r\nOr you want to set it to a \"bot\" account ...\r\n\r\nin all cases you at the moment have to change that in the database manually :/ - change that!\r\n\r\nNOTE: the repair now set it to the current user: #4128",[2958],{"name":2933,"color":2934},571,"let repo admin change the user account who do the api to send back the status","2024-09-20T21:24:09Z","https://github.com/woodpecker-ci/woodpecker/issues/571",0.7474067,{"description":2965,"labels":2966,"number":2968,"owner":2874,"repository":2875,"state":2876,"title":2969,"updated_at":2970,"url":2971,"score":2972},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nThe list of repositories is not updated, when one is added by other another user.\r\nYou either have to logout and login again, or go directly to the new repository.\r\n\r\nLogging in is a bit slow, maybe because of this repository list updating, so if that is caused by checking which repos to show in the list, then that cannot be done on each refresh without speeding it up.\r\n\r\nMaybe a button for manual refresh of the list is enough.\r\n\r\n# Reproduction steps\r\n\r\n1. Log in to Woodpecker as user A\r\n2. Log in to Woodpecker as user B in another browser session\r\n3. As user B, add a Github repository to Woodpecker (/repos/add), it must be a repo that user A also has access to.\r\n4. Refresh the Woodpecker overview of repositories (/repos) as user A\r\n\r\nThe newly added repo will not be on the list of activated repos.\r\n\r\n## Expected\r\n\r\nThe new added repo should be shown.\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-aeb7bcb26a\"}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nGithub Forge\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/80a237c6f19500ba91bbca673f268dfbff7d95f5/server/api/login.go#L169\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).",[2967],{"name":2868,"color":2869},2761,"Repos are hidden until logout => login","2023-11-21T14:23:58Z","https://github.com/woodpecker-ci/woodpecker/issues/2761",0.74915,{"description":2974,"labels":2975,"number":2977,"owner":2874,"repository":2875,"state":2978,"title":2979,"updated_at":2980,"url":2981,"score":2982},"### Component\n\nagent\n\n### Describe the bug\n\nOn an arm64 agent (Raspberry Pi 4b+), the clone step fails when the container is running in podman:\r\n\r\n```\r\n+ git init -b main\r\nInitialized empty Git repository in /woodpecker/src/git.vdx.hu/voidcontext/nix-config/.git/\r\n+ git config --global --replace-all safe.directory /woodpecker/src/git.vdx.hu/voidcontext/nix-config\r\n+ git remote add origin https://git.vdx.hu/voidcontext/nix-config.git\r\n+ git fetch --no-tags --depth=1 --filter=tree:0 origin +a4b83a869d6366bf24921b8f4f3f5836f806f57e:fatal: unable to access 'https://git.vdx.hu/voidcontext/nix-config.git/': Could not resolve host: git.vdx.hu\r\nexit status 128\r\n```\r\n\r\nThe server is on a different server (on amd64).\r\n\r\nExample: https://woodpecker.ci.vdx.hu/repos/109/pipeline/119/5\r\n\r\nThe same pipeline is successful on an amd64 agent (Kubernetes on a 3rd machine).\r\n\r\nThe issue seems to be similar to https://github.com/woodpecker-ci/woodpecker/issues/1407 which has been closed bacause of inactivity.\n\n### Steps to reproduce\n\n1) install server on amd64 machine (A)\r\n2) install agent on arm64 machine (B) using Docker backend that points to a docker compatible podman socket.\r\n3) Run pipeline\n\n### Expected behavior\n\nGit is able to resolve the host as it has a public DNS record.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.6.0\"}\r\n```\n```\n\n\n### Additional context\n\nUnfortunately I wasn't able to test this on `next`.\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]",[2976],{"name":2868,"color":2869},3892,"closed","Git clone step fails with \"Could not resolve host\" error when running fetch","2024-07-18T22:49:20Z","https://github.com/woodpecker-ci/woodpecker/issues/3892",0.68157953,["Reactive",2984],{},["Set"],["ShallowReactive",2987],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fKEH2EnhiyyNXLxfrRK6bZvxxJsAd5Mrp1VHIPU-cKRA":-1},"/woodpecker-ci/woodpecker/4137"]