\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]",[2037,2040],{"name":2038,"color":2039},"bug","d73a4a",{"name":1999,"color":2000},4677,"`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.77136606,{"description":2047,"labels":2048,"number":2052,"owner":1988,"repository":1989,"state":2053,"title":2054,"updated_at":2055,"url":2056,"score":2057},"... move the details from https://woodpecker-ci.org/docs/next/usage/pipeline-syntax#images-from-private-registries to https://woodpecker-ci.org/docs/next/usage/registries and link there instead ...\r\n\r\nand also make it clear in the WebUI that registry tab in repo settings is only for pull images by the agent and not for push via some plugin",[2049],{"name":2050,"color":2051},"documentation","7D625D",1408,"closed","Docs: move private registry infos","2023-10-17T08:31:09Z","https://github.com/woodpecker-ci/woodpecker/issues/1408",0.67183536,{"description":2059,"labels":2060,"number":2062,"owner":1988,"repository":1989,"state":2053,"title":2063,"updated_at":2064,"url":2065,"score":2066},"### 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]",[2061],{"name":2038,"color":2039},3689,"Stuck on login screen. ","2024-06-21T08:20:32Z","https://github.com/woodpecker-ci/woodpecker/issues/3689",0.7109492,{"description":2068,"labels":2069,"number":2071,"owner":1988,"repository":1989,"state":2053,"title":2072,"updated_at":2073,"url":2074,"score":2075},"### 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).",[2070],{"name":2038,"color":2039},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.71379673,{"description":2077,"labels":2078,"number":2080,"owner":1988,"repository":1989,"state":2053,"title":2081,"updated_at":2082,"url":2083,"score":2084},"### Component\n\nserver, agent\n\n### Describe the bug\n\nIf you try to set proxy related env vars in a pipeline step, they won't get used. They are present but without the given values:\r\n\r\n```yaml\r\nwhen:\r\n - event: [pull_request, tag, cron]\r\n - event: push\r\n branch:\r\n - ${CI_REPO_DEFAULT_BRANCH}\r\n - renovate/*\r\n\r\nvariables:\r\n - &golang \"golang:1.21\"\r\n - proxy_args: &proxy_args\r\n - \"http_proxy=http://swarmproxy:8888\"\r\n - \"https_proxy=http://swarmproxy:8888\"\r\n - \"no_proxy=.myhost.com\"\r\n - \"TESTENV=DEBUGGING\"\r\nsteps:\r\n test:\r\n image: *golang\r\n environment:\r\n - \u003C\u003C: *proxy_args\r\n commands:\r\n - env | sort\r\n - go test -cover ./...\r\n```\r\n\r\nThe output looks like this:\r\n\r\n```shell\r\n....\r\nGOLANG_VERSION=1.21.4\r\nGOPATH=/go\r\nGOTOOLCHAIN=local\r\nHOME=/root\r\nHOSTNAME=45d463959e69\r\nHTTPS_PROXY=\r\nHTTP_PROXY=\r\nNO_PROXY=\r\nPATH=/go/bin:/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin\r\nPWD=/woodpecker/src/xxxxxx/Templates/plugin-extend-env\r\nSHELL=/bin/sh\r\nTESTENV=DEBUGGING\r\nhttp_proxy=\r\nhttps_proxy=\r\nno_proxy=\r\n+ go test -cover ./...\r\ngo: downloading github.com/urfave/cli/v2 v2.25.7\r\ngo: downloading github.com/sirupsen/logrus v1.9.3\r\ngo: downloading github.com/Masterminds/semver/v3 v3.2.1\r\ngo: downloading github.com/joho/godotenv v1.5.1\r\nsemver.go:6:2: github.com/Masterminds/semver/v3@v3.2.1: Get \"https://proxy.golang.org/github.com/%21masterminds/semver/v3/@v/v3.2.1.zip\": dial tcp: lookup proxy.golang.org on 127.0.0.11:53: no such host\r\ntools.go:3:8: github.com/joho/godotenv@v1.5.1: Get \"https://proxy.golang.org/github.com/joho/godotenv/@v/v1.5.1.zip\": dial tcp: lookup proxy.golang.org on 127.0.0.11:53: no such host\r\nlogger.go:6:2: github.com/sirupsen/logrus@v1.9.3: Get \"https://proxy.golang.org/github.com/sirupsen/logrus/@v/v1.9.3.zip\": dial tcp: lookup proxy.golang.org on 127.0.0.11:53: no such host\r\nflags.go:4:2: github.com/urfave/cli/v2@v2.25.7: Get \"https://proxy.golang.org/github.com/urfave/cli/v2/@v/v2.25.7.zip\": dial tcp: lookup proxy.golang.org on 127.0.0.11:53: no such host\r\n...\r\n```\n\n### System Info\n\n```shell\n{\r\n \"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n \"version\": \"1.0.5\"\r\n}\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\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]\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).",[2079],{"name":2038,"color":2039},2858,"Proxy environment variables not passed through in pipeline steps","2023-12-03T16:50:09Z","https://github.com/woodpecker-ci/woodpecker/issues/2858",0.7200914,{"description":2086,"labels":2087,"number":2091,"owner":1988,"repository":1989,"state":2053,"title":2092,"updated_at":2093,"url":2094,"score":2095},"### Clear and concise description of the problem\n\nThe [docs](https://woodpecker-ci.org/docs/administration/setup) show that the agent needs access to the docker socket. It's good practice to use a proxy instead of exposing the entire socket. The most common is the [\"tecnativa\" proxy](https://github.com/Tecnativa/docker-socket-proxy) .\r\n\r\nI assume that at the very least, an agent creates new containers, so needs access to the \"containers\" endpoint. Presumably it needs other endpoints too.\n\n### Suggested solution\n\nPlease consider *documenting which parts of the docker api are needed by the agent*. Then we could use the docker socket proxy to allow those and restrict the others.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\nThese are [the docker api's endpoints](https://github.com/Tecnativa/docker-socket-proxy#grant-or-revoke-access-to-certain-api-sections):\r\n- typically allowed:\r\n - EVENTS\r\n - PING\r\n - VERSION\r\n- security-critical and so typically not allowed:\r\n - AUTH\r\n - SECRETS\r\n - POST\r\n- other\r\n - BUILD\r\n - COMMIT\r\n - CONFIGS\r\n - CONTAINERS\r\n - DISTRIBUTION\r\n - EXEC\r\n - GRPC\r\n - IMAGES\r\n - INFO\r\n - NETWORKS\r\n - NODES\r\n - PLUGINS\r\n - SERVICES\r\n - SESSION\r\n - SWARM\r\n - SYSTEM\r\n - TASKS\r\n - VOLUMES\r\n\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 [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\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.",[2088],{"name":2089,"color":2090},"feature","180DBE",1917,"Use woodpecker with docker socket proxy","2023-08-20T16:09:23Z","https://github.com/woodpecker-ci/woodpecker/issues/1917",0.7318329,["Reactive",2097],{},["Set"],["ShallowReactive",2100],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"qOmYsJVEceJEpd-zJ1I1KUKswtJs_uHBYoWmD_yl5y8":-1},"/woodpecker-ci/woodpecker/2982"]